Hi Martynas, Ah, nice. I will try that out as a starting point.
The documentation only shows *ClusterClient* requests. If I want to update data on a websocket (e.g. cluster nodes online), I would have to implement a polling strategy? Like scheduling a *ClusterState* message to a *ClusterMonitor* actor. thanks, Muki Am Montag, 7. Juli 2014 23:02:16 UTC+2 schrieb Muki: > > Hi, > > I'm currently starting to learn more about akka's cluster feature. > My goal is to have separate frontend and backend which are part > of the same cluster, so I can > > > - Start jobs on backend akka-nodes from the play frontend-nodes > - Monitor my cluster status (nodes up/down, jobs running) > - Update backend and frontend independently > > > That being said, I'm struggling what is the best way to achieve this. > > > 1. Should I create two ActorSystems in my play application. The > internal, play managed one, which > is harder to configure (e.g. name is static to *play*) > 2. Should I use remoting instead of clustering? > > I tried solution number 1, but the websocket actors couldn't be created, > because *ActorRefClusterProvider* > wasn't configured (but it's in the config, when I log it via > system.logConfiguration). > > thanks for any advice, > Muki > -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
