You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WARNING
ActorPublisher class and ActorSubscriber class will probably be deprecated in future versions of Akka.
What is the recommended approach?
One tends to want to wrap a source resource up in an Actor (say to call a REST API that returns batches of results) and pipe those results into a stream, but have back pressure to only get the next batch when down steam can handle them.
The WebCrawler sample uses the Actor as a Coordinator but then you lose out on the Actor wrapping the source on its own so you break your API encapsulation.
Also much of the documentation related to article that is linked in issues related to Streams, or on the Petabridge site seem to be broken.
Thanks for any insights.
The text was updated successfully, but these errors were encountered:
Per:
https://getakka.net/articles/streams/integration.html#implementing-reactive-streams-publisher-or-subscriber
What is the recommended approach?
One tends to want to wrap a source resource up in an Actor (say to call a REST API that returns batches of results) and pipe those results into a stream, but have back pressure to only get the next batch when down steam can handle them.
The WebCrawler sample uses the Actor as a Coordinator but then you lose out on the Actor wrapping the source on its own so you break your API encapsulation.
Also much of the documentation related to article that is linked in issues related to Streams, or on the Petabridge site seem to be broken.
Thanks for any insights.
The text was updated successfully, but these errors were encountered: