raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 10

+htc #18027 add the missing javadsl.clientLayer and serverLayer

Browse source
This commit is contained in:
Johannes Rudolph 2015-07-24 10:57:54 +02:00
parent e14773c3d9
commit 8ef7c64886
7 changed files with 110 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

2
akka-docs-dev/rst/scala/http/client-side/connection-level.rst
View file

@ -67,7 +67,7 @@ However, akka-stream should soon provide such a feature.
Stand-Alone HTTP Layer Usage
----------------------------
Due to its Reactive-Stream-based nature the Akka HTTP layer is fully detachable from the underlying TCP
Due to its Reactive-Streams-based nature the Akka HTTP layer is fully detachable from the underlying TCP
interface. While in most applications this "feature" will not be crucial it can be useful in certain cases to be able
to "run" the HTTP layer (and, potentially, higher-layers) against data that do not come from the network but rather
some other source. Potential scenarios where this might be useful include tests, debugging or low-level event-sourcing

4
akka-docs-dev/rst/scala/http/low-level-server-side-api.rst
View file

@ -155,13 +155,13 @@ If defined encryption is enabled on all accepted connections. Otherwise it is di
Stand-Alone HTTP Layer Usage
----------------------------
Due to its Reactive-Stream-based nature the Akka HTTP layer is fully detachable from the underlying TCP
Due to its Reactive-Streams-based nature the Akka HTTP layer is fully detachable from the underlying TCP
interface. While in most applications this "feature" will not be crucial it can be useful in certain cases to be able
to "run" the HTTP layer (and, potentially, higher-layers) against data that do not come from the network but rather
some other source. Potential scenarios where this might be useful include tests, debugging or low-level event-sourcing
(e.g by replaying network traffic).
On the server-side the stand-alone HTTP layer forms a ``BidiStage`` that is defined like this:
On the server-side the stand-alone HTTP layer forms a ``BidiFlow`` that is defined like this:
.. includecode2:: /../../akka-http-core/src/main/scala/akka/http/scaladsl/Http.scala
:snippet: server-layer