fhttp-core

License	APL2
Categories	Net React User Interface Web Frameworks
GroupId	net.reactivecore
ArtifactId	fhttp-core_2.12
Last Version	0.3.0
Release Date	Apr 23, 2021
Type	jar
Description	fhttp-core fhttp-core
Project URL	https://github.com/reactivecore/fhttp
Project Organization	net.reactivecore
Source Code Management	https://github.com/reactivecore/fhttp

Download fhttp-core_2.12

Filename	Size
fhttp-core_2.12-0.3.0.pom
fhttp-core_2.12-0.3.0.jar	79 KB
fhttp-core_2.12-0.3.0-sources.jar	5 KB
fhttp-core_2.12-0.3.0-javadoc.jar	1 MB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/net.reactivecore/fhttp-core_2.12/ -->
<dependency>
    <groupId>net.reactivecore</groupId>
    <artifactId>fhttp-core_2.12</artifactId>
    <version>0.3.0</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/net.reactivecore/fhttp-core_2.12/
implementation 'net.reactivecore:fhttp-core_2.12:0.3.0'

Gradle Kotlin

// https://jarcasting.com/artifacts/net.reactivecore/fhttp-core_2.12/
implementation ("net.reactivecore:fhttp-core_2.12:0.3.0")

Apache Buildr

'net.reactivecore:fhttp-core_2.12:jar:0.3.0'

Apache Ivy

<dependency org="net.reactivecore" name="fhttp-core_2.12" rev="0.3.0">
  <artifact name="fhttp-core_2.12" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='net.reactivecore', module='fhttp-core_2.12', version='0.3.0')
)

Scala SBT

libraryDependencies += "net.reactivecore" % "fhttp-core_2.12" % "0.3.0"

Leiningen

[net.reactivecore/fhttp-core_2.12 "0.3.0"]

Dependencies

compile (4)

Group / Artifact	Type	Version
org.scala-lang : scala-library	jar	2.12.13
com.chuusai : shapeless_2.12	jar	2.3.4
io.circe : circe-generic_2.12	jar	0.13.0
io.circe : circe-parser_2.12	jar	0.13.0

test (1)

Group / Artifact	Type	Version
org.scalatest : scalatest_2.12	jar	3.0.9

Project Modules

There are no modules declared in this project.

fhttp, functional Http-Api definition in Scala

fhttp is a little proof of concept, whether it's possible to define a HTTP-API in a functional manner without binding directly to a framework.

From the definition it should be possible to generate Server and Client implementations without that much boilerplate.

The definition should not have any dependencies to the Server/Client library.

Current State

This is a proof of concept. Although it works, expect bugs everywhere. There are no published packages.

How it works

Each ApiCall instance is made of various transitions, stored in a full typed shapeless HList.

The Framework Implementation (at the moment only Akka HTTP) lifts this list into an Encoder / Decoder for HTTP-Requests and their response.

Parts

• core Definition system
• akka Implementation for Akka HTTP
• example A simple Example

Features

• Support for path adding/extracting
• Support for Circe JSON, Strings
• Support for async file upload and download
• Support Query Parameters.
• Elegant transport for errors in error responses.

TODO

• Testing
• Better error handling
• Better path handling
• More HTTP Methods (right now only GET, POST and DELETE)
• Support for optional values
• Improved conversion routines (e.g. Boolean query parameters)
• Get rid of VTree if possible.
• Reduce number of Future mappings if possible.
• Extending
• Multi part decoding on Akka Server side buffers the request in Memory.

Reactive Core GmbH

Versions

Version
0.3.0 Apr 23, 2021
0.2.2 Jul 27, 2020
0.2.1 Aug 21, 2019
0.1.2 Aug 14, 2019