actor

I'm just going through the javadoc and various tutorials on libgdx and I'm at the stage of trying to figure out differences between various concepts that seem similar to me or provide similar capabilities in libgdx. At first I thought scene2d was about creating interactive items such as menus, etc but various tutorials I'm reading use scene2d/actors for the main game items (i.e. the player, etc) and others just use sprites. What exactly is the difference between using Sprite and Actor (i.e. scene2D) in a game and when should you choose? Thanks. A Sprite is basically an image with a position,

Recently i have been getting into alternative languages that support an actor/agent/shared nothing architecture - ie. scala, clojure etc (clojure also supports shared state). So far most of the documentation that I have read focus around the intro level. What I am looking for is more advanced documentation along the gang of four but instead shared nothing based. Why ? It helps to grok the change in design thinking. Simple examples are easy, but in a real world java application (single threaded) you can have object graphs with 1000's of members with complex relationships. But with agent based

Right now I'm looking at Play Framework and like it a lot. One of the parts heavy advertised amongst the features offered in Play is Akka . In order to better understand Akka and how to use it properly, can you tell me what are the alternatives in other languages or products? How does RabbitMQ compare to it? Is there a lot of overlap? Is it practical using them together? IN what use cases? The best place to start is a great Akka official documentation . I think the closest product/framework to Akka is erlang language. I guess (I haven't used Play framework) Akka is used there to implement

What is the difference between exclamation mark ( ! ) and question mark ( ? ) when sending messages to Actors? myActor ! Hello(value1) myActor ? Hello(value1) om-nom-nom Shamelessly copied [awesome] official doc (look Send messages section for more): Messages are sent to an Actor through one of the following methods. ! means “fire-and-forget”, e.g. send a message asynchronously and return immediately. Also known as tell . ? sends a message asynchronously and returns a Future representing a possible reply. Also known as ask . mattinbits From the recipient's point of view, it sees tell and ask

I've been looking into learning erlang, and as a result, have been reading (okay, skimming) about the actor model. From what I understand, the actor model is simply a set of functions (run within lightweight threads called "processes" in erlang), which communicate with each other only via message passing. This seems fairly trivial to implement in C++, or any other language: class BaseActor { std::queue<BaseMessage*> messages; CriticalSection messagecs; BaseMessage* Pop(); public: void Push(BaseMessage* message) { auto scopedlock = messagecs.AquireScopedLock(); messagecs.push(message); }

I apologize for the long question. I have been experimenting with Orleans to know about its various properties and these questions are logically under one umbrella. The first test involved making request from client to a specific grain every 1 second while the grain takes 10 seconds to execute the requests. The code is this: // client code while (1) { Console.WriteLine("Client giving another request"); double temperature = random.NextDouble() * 40; var sensor = client.GetGrain<ITemperatureSensorGrain>(500); Task t = sensor.SubmitTemperatureAsync((float)temperature); Console.WriteLine(t.Status)

I have a scenario where I have some objects that need to take in references from each other. The only way I can get this to compile is to use lazy class A(b:B) class B(a:A) lazy val a:A = new A(b) lazy val b:B = new B(a) I can do the same thing using some actors, and get it to compile also abstract class Message case class Message1 extends Message case class Message2 extends Message class Actor1(otherActor:Actor) extends Actor { def act() { loop { react { case Message1 => println("received message1") otherActor ! Message2 case _ => } } } } class Actor2(otherActor:Actor) extends Actor { def act