It's a work in progress, but this is what I came up with until now: I think it's best to get rid of the controller. It's main purpose is to decouple the view from the model allowing to replace the view with another one without changing the model. But actor messages do the same, so a controller is not needed for this. (The message classes must then be placed outside the actor class inside their own public interface to have a real exchangeability).
Disadvantage: Without a controller there is no single intersection where messages/events must pass, so a gap-less logging inside all actors' onReceive method must be ensured. What do you guys think? Would you instead prefer to have a controller actor that receives all messages from the model and forwards them to the view (and backwards the same)? -- >>>>>>>>>> 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 [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/d/optout.
