Am Mittwoch, 5. Februar 2014 11:40:34 UTC+1 schrieb ajlopez: > > The cons: the wait or requeue the command. shared id list, precluding > distributed actors (I could imagine a machine by hash slot in Alsing > original solution) > The pros: in one actor fails, it only affect a command, instead of a group > of hashed entities, that could be thousands? >
I don't really understand what the advantage of the shared list is. First of all, sharing state in actors is considered harmful in general. and there is an advantage here that would justify going for it. Secondly, the commands are preserved in the mailboxes of the child actors (if you restart them on failure). If you want your commands to survive failure of the whole actor system, you need persistence anyway. So I think using a shared list is the wrong path. While your solution would work, there are better solutions within Akka. best Carsten -- >>>>>>>>>> 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.
