>From what I know, RS specify that a producer can only push data when there is demand for it downstream, in order to avoid flooding the downstream. Think about a case where the producer produces a huge amount of messages before the downstream even time to react and ask it to throttle itself - that could easily cause the downstream to crash. This way, the if the downstream is able to handle, say, 1000 messages it requests 1000 messages and the publisher can send 1000 messages as they become ready. But in order to send the 1001st message, it would have to wait for further requests from the downstream.
Hope this makes sense, Tal On Sunday, January 31, 2016 at 2:56:40 PM UTC+2, john....@gmail.com wrote: > > By looking at the API of akka.stream.actor.AbstractActorPublisher I > conclude that it only reacts to ActorPublisherMessage.Request messages. > > It always has to first receive a ActorPublisherMessage.Request before it > can send data by onNext(). > > Please forgive if I am wrong but I thought that "Reactive Streams > specification" also allows a Publisher to actively push data downstream. > (of course if it pushes too fast it will receive a throttling message) > > This seems to not be possible with the current > akka.stream.actor.AbstractActorPublisher > API? > > > > > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
