> In layman's terms this means that changes to internal fields of the actor are visible when the next message is processed by that actor. > So fields in your actor need not be volatile or equivalent. I apologize if this has been asked before, but how does akka guarantee that when the actor is scheduled back and forth between threads, each thread will see the correct (latest) version of the actor state? I guess my question is how is this implemented internally in akka?
Also, what if my actor state contains references to mutable objects? I understand I don't have to worry about the actor fields themselves, but what about the mutable objects they refer to? Are those synchronized automatically by akka for me as well? And if so, can we make the docs a bit more explicit about this? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/groups/opt_out.
