> > Why don’t you normally shard actors of the same kind who will just > supervise these different stream handlers?
Wow, this is actually a brilliant idea and it certainly reduced the complexity of my original solution. I remember I had tried something similar where instead of passing in a Props object I tried passing in the actual parameters into the StreamActor but it ended up getting too complicated. I hadn't thought of passing in an actual Props object into another actor that would then create a StreamActor as its child using this Props. Thank you for the suggestion, it worked out quite nicely! I think same instance was used for several entry types, i.e. several > ShardCoordinator instances and therefore it must be thread safe. Yep, you got it Patrik. It needed to be thread safe. -- >>>>>>>>>> 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.
