ok, I was playing around with this yest. there is no way to do that. only mapAsync is a way to create a flow that pushes elements of the stream to 3rd party components such as actors. this is a bit confusing as there is a ActorPublisher that would be good fit here if only Flow had a construct like Source.actorPublisher() / Sink. actorRef(). this way we could pass Props of publisher which would transform incoming messages into something else.
On Monday, 7 March 2016 11:28:03 UTC+1, paweł kamiński wrote: > > yep, i'm now thinking about duplex flow so I can push incoming messages to > actorRef sink and then such actor would be a source. > > I must say that constructing right flow is not an easy task if you do it > occasionally! :) > maybe I ll share my findings once I get it working > > On Monday, 7 March 2016 10:43:26 UTC+1, Rafał Krzewski wrote: >> >> W dniu poniedziałek, 7 marca 2016 10:08:23 UTC+1 użytkownik paweł >> kamiński napisał: >> >>> thanks for response. >>> >>> well ask pattern is a way to go but I thought I could avoid it and use >>> only flow's connection. >>> >>> Akka gives you a rich choice of communication primitives and it's OK to >> mix and match them in a way that solves the problem at hand in most >> convenient way :) >> >> Happy hacking! >> Rafał >> > -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
