Then you’d have to encode the message type into the Actor ref, which would drastically decrease the value of something like the ActorRegistry. Also, with powerful mechanics like “become” (which is fundamental to the actor model) typing the messages is less valuable. Since Akka doesn’t leak memory when a message is not matched to the … Read more
To make actors with gevent, use a Greenlet subclass with embedded gevent.queue.Queue instance used as an inbox. To read a message from the inbox, simply get() from the queue. To send a message to an actor, put it into that actor’s queue. Read about subclassing Greenlet here. If you need help with writing the Actor … Read more
Given some concurrency problem, what would you look for to decide whether to use actors or not? First I would look to define the problem… is the primary motivation a speedup of a nested for loop or recursion? If so a simple task based approach or parallel loop approach will likely work well for you … Read more
Avoid !? wherever possible. You will get a locked system! Always send a message from an Actor-subsystem thread. If this means creating a transient Actor via the Actor.actor method then so be it: case ButtonClicked(src) => Actor.actor { controller ! SaveTrade(trdFld.text) } Add an “any other message” handler to your actor’s reactions. Otherwise it is … Read more
That definition of an Actor actually seems a little restrictive. It certainly doesn’t handle Erlang-style actors (or I believe Scala-style actors). In my experience, an actor is something that: Sends and receives messages (each actor has a mailbox) Shares no mutable memory with other actors Is scheduled based on the whims of the runtime. An … Read more
This is the most comprehensive comparison I have seen so far: http://doc.akka.io/docs/misc/Comparison_between_4_actor_frameworks.pdf via http://klangism.tumblr.com/post/2497057136/all-actors-in-scala-compared
The sender() will be different on the receiving end. Message sends using tell (also known as !): A tells message M to B. B tells that message to C. C thinks the sender() of message M is B. Message sends using forward: A tells message M to B. B forwards that message to C. C … Read more
It indicates a Symbol. Eg. cfr http://www.scala-lang.org/docu/files/api/scala/Symbol.html : the Scala term ‘mysym will invoke the constructor of the Symbol class in the following way: Symbol(“mysym”).
In your original code, you only started one MailboxProcessor. Make wait() a function, and call it with each yield. Also you are not waiting for them to spin up or receive the messages, which I think invalidates the timing info; see my code below. That said, I have some success; on my box I can … Read more
This is related to a previous question, if not exactly the same! It’s not such a simple question because the actor model of concurrency allows for many different types of applications to be built, from a stateful single-VM application (with a few separate actor classes) to a stateless cluster of thousands of instances of an … Read more