I'm trying to make a cluster with one manager and multiple workers. As a greenhorn in akka clusters I first googled around. I've found plenty of examples for clusters running on a single JVM, which to me, is an antinomy. And I've found a handful of examples running on different JVMs on the same node. Thats already something, but only half of the story: these examples simply copied or used ALL of the cluster code to all JVMs and started the actor systems with all the worker AND manager code in the classpath. But that's ugly and not what I want. I'd like to nicely separate the code dedicated to the manager form the code dedicated to the workers (and possibly the common code). I don't like manager code on the worker nodes or worker code on the manager nodes (actor systems).
I succeeded to do this with remoting (sending a string message to a remote actor (system)). I'd like to do this in a cluster. I'd like to keep it as simple as possible (no special routing policy necessary, actors may join manually, ...) Can you please help me to overcome my stupidity? Klaus W, -- >>>>>>>>>> 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.
