Doc statement no longer true with new Actor APIs (#28924)
This commit is contained in:
parent
acfb8c44e3
commit
5a2e43b2d9
1 changed files with 1 additions and 3 deletions
|
|
@ -19,9 +19,7 @@ measures in order to achieve stable streaming between actors, since in addition
|
||||||
to sending and receiving we also need to take care to not overflow any buffers
|
to sending and receiving we also need to take care to not overflow any buffers
|
||||||
or mailboxes in the process. Another pitfall is that Actor messages can be lost
|
or mailboxes in the process. Another pitfall is that Actor messages can be lost
|
||||||
and must be retransmitted in that case. Failure to do so would lead to holes at
|
and must be retransmitted in that case. Failure to do so would lead to holes at
|
||||||
the receiving side. When dealing with streams of elements of a fixed given type,
|
the receiving side.
|
||||||
Actors also do not currently offer good static guarantees that no wiring errors
|
|
||||||
are made: type-safety could be improved in this case.
|
|
||||||
|
|
||||||
For these reasons we decided to bundle up a solution to these problems as an
|
For these reasons we decided to bundle up a solution to these problems as an
|
||||||
Akka Streams API. The purpose is to offer an intuitive and safe way to
|
Akka Streams API. The purpose is to offer an intuitive and safe way to
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue