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

=doc port over some http documentation from the scala side

Browse source
This commit is contained in:
Johannes Rudolph 2015-07-10 19:13:56 +02:00
parent 16d4b4a331
commit 11d98a6593
18 changed files with 701 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

8
akka-docs-dev/rst/scala/http/common/http-model.rst
View file

@ -72,8 +72,8 @@ Here are some examples how to construct an ``HttpResponse``:
.. includecode:: ../../code/docs/http/scaladsl/ModelSpec.scala
:include: construct-response
In addition to the simple ``HttpEntity`` constructors create an entity from a fixed ``String`` or ``ByteString`` shown
as here the Akka HTTP model defines a number of subclasses of ``HttpEntity`` which allow body data to be specified as a
In addition to the simple ``HttpEntity`` constructors which create an entity from a fixed ``String`` or ``ByteString``
as shown here the Akka HTTP model defines a number of subclasses of ``HttpEntity`` which allow body data to be specified as a
stream of bytes.
@ -93,9 +93,9 @@ HttpEntity.Strict
HttpEntity.Default
The general, unchunked HTTP/1.1 message entity.
It has a known length and presents its data as a ``Source[ByteString]`` which can only materialized once.
It has a known length and presents its data as a ``Source[ByteString]`` which can be only materialized once.
It is an error if the provided source doesn't produce exactly as many bytes as specified.
On the wire, a ``Strict`` entity and a ``Default`` entity cannot be distinguished.
The distinction of ``Strict`` and ``Default`` is an API-only one. One the wire, both kinds of entities look the same.
HttpEntity.Chunked