Closely related to this question <https://groups.google.com/forum/#!searchin/akka-user/streams$20actors/akka-user/AxVI8T_laYg/Qsi3BfCzQMwJ>, I know that Akka Streams do not yet support remote materialisation, but what if you want to have Akka Streams handle a local graph of stream processing, and have some intermediate processing work done by existing (possibly remote) actors? The way I would approach it is to have an ActorSubscriber as a sink to talk to each actor and an ActorPublisher as a source to receive results for each actor, but this is likely to lead to multiple flows or graphs that are disconnected from each other. Is there any more elegant way to approach it?
-- >>>>>>>>>> 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 http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
