Joshua Rodrigues wrote:1. I know that concurrency means multithreading but how does multithreading relate to Actors?
Joshua Rodrigues wrote:2. What does it mean when Actors do not have a shared state? What is this "state" exactly? And how do Actors not have a shared state between each other?
Joshua Rodrigues wrote:3. What does the Actor Model "achieve" exactly?
Joshua Rodrigues wrote:4. "Messages" within Actors could be basically anything you wish to send from one Actor to another? An example would be great here!
Joshua Rodrigues wrote:5. How do Actors create parallel execution as stated here on this site.
Joshua Rodrigues wrote:6. How do Actors have an advantage over Threads? Amount of memory used, the amount of Actors to Threads ratio, the message-passing effect, etc.
Joshua Rodrigues wrote:Just two more questions - the first one is about Event-Driven Actors. When it comes down to Events, do Events process the Messages, redirect the Messages elsewhere, or what exactly? What exactly does an Event do within the Actor Model? In my project that contains Actors, Events handle the Messages. Is this correct or am I doing something wrong?
Joshua Rodrigues wrote:Second Question - running multiple Actors concurrently? Do the Actors themselves become concurrent or do the Messages become concurrent or both maybe? When it comes down to concurrency, I usually use the newFixedThreadPool - which is what I am using for messages (wrong or correct?). How would I go about using a ThreadPool for Actors? Would I need to make the Actor extend the Runnable interface and then submit the Actor into the new newFixedThreadPool? Sorry, I'm still kind of new to concurrency and Actors.