How can I use an actor to store/read state information correctly so the MyObj can use it to read and set state? You cannot mutate an actor’s instance variables from outside the actor. That is the whole point of actors! Instead, give the actor a method that sets its own instance variable. You will then … Read more
A Sprite is basically an image with a position, size, and rotation. You draw it using SpriteBatch, and once you have your your Sprites and your SpriteBatch, you have a simple, low-level way to get 2D images on the screen anywhere you want. The rest is up to you. Actor, on the other hand, is … Read more
This is due to type-erasure. The JVM does not know of any type parameter, except on arrays. Because of that, Scala code can’t check whether an Option is an Option[Int] or an Option[String] — that information has been erased. You could fix your code this way, though: object Test { def test = { (Alice … Read more
Yes, this is possible with Akka. There are 2 ways to achieve this as far as I know: akka-remote – Provides remote actor ref, but you need to decide where each actor should exsist. akka-cluster – Provides cluster sharding. Automatically manages actor physical location and ensures that given shard (Actor) is present on at most … Read more
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