Thank you very much for your response. I have a question, as I am just learning the framework and I am more familar with Java than Scala.
The "trick" to dealing with Akka Persistence seems to be that the Actor itself encapsulates state, and the transition is done by replacing the old state with a new state in the function that is a parameter to the persist method. That way, you can replay it later when restarting the actor. Is this a good enough summary (sorry if I am using the terms not precisely)? That would mean that developing such an application could be quite different from developing a local application, where state is spread over many objects. (Or rather, the only way to change state in another object would be that the other object is an Actor as well and it receives an event that is raised. But what if it does not receive the event during replay? Wouldn't that corrupt the overall state of the application?) Is that description correct? Thanks. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
