On Tue, Mar 25, 2014 at 2:40 AM, Patrik Nordwall <[email protected]>wrote:
> Yes, then different Foos can have different timeouts, by deciding > themselves. Might even depend on the data, e.g. WIP Customer stays in > memory longer. > Yeah, I was just realizing that part of our different viewpoints here is because of the different use cases. The Cluster Sharding manager is typically controlling *heterogeneous* children -- it will routinely have a number of child Actors of different sorts. For that case, I agree that it makes far less sense to bundle the semantics into the Manager. But I'm focused on the fairly common (but less general) situation where the Manager has a bunch of relatively *homogeneous* children, each of which has its own data but is essentially the same type: I have a bunch of "Foo" Actors, and specifically a FooManager. That is leading me to focus on different priorities, and makes the correct separation of concerns less obvious. I *think* that in that sort of situation it's typically going to be more straightforward to put the timeout handling in the Manager. We'll see. I think I'm going to try it that way, and we can see whether the resulting API turns out to make sense in practice. If nothing else, it should provide an interesting alternative to compare against... -- >>>>>>>>>> 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.
