Hi Rafal, thank you for your interest. And Yes, I understand the benefits of one single source. And thats how they do it on the internet tutorials.
But these things get questionable if 1. the managers task of finding out what a worker should do is complicated in algorithm (and thus in code, take about 1 MB of code) and has absolutely nothing to do with the workers algorithm (and code) 2. the worker's task, however, is all the same for, say, 10000 workers and totally independent from the manager logic. May be there is a tiny common part (the message types?). But it really would be a bad idea to add manager code to all the worker nodes. I really like all those tutorials explaining this or another feature of Akka Clusters. But I would also really like a realistic example (IMHO the above list is quite realistic) reduced to the min and explained with simple (but complete) code including configuration. Btw. I feel really stupid that I did not succeed yet to derive one from the mentioned tutorials myself. Thanks once again. Klaus -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
