> > >> Which generates an `Actor` backed producer for you (that will call your >> function), or if you need complete control you can implement a >> `Producer[T]` and give it to `Flow`: >> > > I don't think that is enough. It assumes that the elements are available > when calling the closure, otherwise blocking will happen. We have one > ticket <https://github.com/akka/akka/issues/15135> for creating a > producer from a closure that returns a future. I think we should have > support for a producer that is an actor also. > Stay tuned. >
Right, I was thinking about a Future-based producer initially as well (I could then use ? to get the data from the actor), but then I thought it would be actually more efficient if I knew how many elements I can produce in the actor. Adam -- >>>>>>>>>> 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.
