Interesting. But isn't this really a question of a custom routing strategy similar to Random, RoundRobin etc? Perhaps a router strategy that is aware of the "remote Akka systems"?
Cheers Oleg On Mon, Feb 10, 2014 at 11:02 AM, bryan hunt <[email protected]>wrote: > > Is there a simple configuration mechanism whereby one might specify a pool > of remote Akka systems upon which a given actor might be found? > > Perhaps something like (pseudoconfig): > > /remote1 { > enabled-transports = ["akka.remote.netty.tcp"] > pool = [ > { hostname = "127.0.0.1", port = 6661 }, > { hostname = "127.0.0.1", port = 6662 } > ] > } > > Forgive the poorly worded question. I haven't used routing for much thus > far. > > Bryan > > -- > >>>>>>>>>> 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. > -- >>>>>>>>>> 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.
