Hi Patrik, > welcome >
Thanks! > I suggest that you use one actor as the consistency boundary. That doesn't > mean you have to structure all code into one actor. You can delegate to > other classes, and you can have other actors performing work and collecting > the sub-results, and then finally when everything is ready perform the > update in one actor. > Currently I have a set of actors that each look after a single document. By look after, I mean they let other actors read the data and receive updated revisions from another system. If I want to update say 5 of these documents in a single transaction then are you suggesting I have one actor responsible for all 5? Cheers, Kevin -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
