That's a really interesting proposal, would you recommend that the master still handles the child actors but just passes them a reference to their newly created aggregated actor at construction?
On Wednesday, 23 April 2014 16:44:24 UTC+1, Richard Cole wrote: > > I'm currently using akka to implement a basic processing workflow. My > MasterActor will receive a message that contains N number of elements > within it. At this point I can divide these elements across Y number of > child actors. If we imagine my elements are peoples names. The child > actors role is to take it's sub-list of names and measure the length of > them, providing the MasterActor with a result once finished. > > What is the most correct way (in the message passing sense) of letting the > MasterActor know that all of it's ChildActors have finished processing > their list of names? > > My main consideration is where there may be multiple requests happening at > once, so a single MasterActor may need to manage multiple requests and > multiple ChildActors. > -- >>>>>>>>>> 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.
