Hi Eugene,
On Sun, May 4, 2014 at 6:23 PM, Eugene Dzhurinsky jdeve...@gmail.comwrote:
On Sun, May 04, 2014 at 09:46:50AM +0200, Heiko Seeberger wrote:
class MyActor(myParameter: String) extends Actor with FSM { ... }
context.actorOf(Props(new MyActor(myArgument)))
As far as I
On Sun, May 4, 2014 at 6:23 PM, Eugene Dzhurinsky jdeve...@gmail.comwrote:
On Sun, May 04, 2014 at 09:46:50AM +0200, Heiko Seeberger wrote:
class MyActor(myParameter: String) extends Actor with FSM { ... }
context.actorOf(Props(new MyActor(myArgument)))
As far as I understand, this will
On Sun, May 4, 2014 at 3:22 AM, Eugene Dzhurinsky jdeve...@gmail.comwrote:
Okay, fine. My question was related to how to create an instance of FSM
actor,
which accepts parameters in it's constructor, however thinking carefully I
think that it's quite possible to pass the initialization stuff
On Sun, May 04, 2014 at 09:46:50AM +0200, Heiko Seeberger wrote:
class MyActor(myParameter: String) extends Actor with FSM { ... }
context.actorOf(Props(new MyActor(myArgument)))
As far as I understand, this will create an actor on the same host/same JVM,
but I need it to be created in a
That's pretty much what we do. We give one of our nodes the supervisor
role and start a ClusterSingletonActor on it which spawns a control FSM (we
call it a Pipeline) which in turn spawns worker FSMs (PipelineWorkers).
Those actors then marshall data and delegate work to stateless actors
On Sat, May 03, 2014 at 04:16:34PM -0700, Ryan Tanner wrote:
That's pretty much what we do. We give one of our nodes the supervisor
role and start a ClusterSingletonActor on it which spawns a control FSM (we
call it a Pipeline) which in turn spawns worker FSMs (PipelineWorkers).
Those
I have one more question, if you please.
It seems that you have a control actor (singleton), which knows about
Pipelines, and the pipelines are actually started in a cluster. And every
pipeline creates its own set of FSM actors *locally**, *passing them the
references to the stateless worker
