I want to use actors in a Java MVC application. One reason is to replace the conventional property-change events by some meaningful messages sent between model actors and view actors.
Although there are many solutions and hints about Akka available that focus on smaller details of Akka and the UI, I couldn't find one for the bigger picture. So, to make it short, my question is: *What is your suggestion to design an actor-based MVC application?* Some considerations: The model: Of course, there will be one or several model actors that wrap the business logic/objects and may supervise child actors for sub-tasks. The view: There will be one or several view actors that update UI panes, canvases, etc. The question here will be whether to use Platform.runLater or other solutions to access the UI thread. The controller: Here is my biggest uncertainty. Should the controller just hold the ActorSystem, instantiate everything, and let the actors talk on their own, or should it keep the central role of a MVC application: that all events must pass by him? By the way, I'm not stuck with MVC. If you suggest that another design like MVP, MVVM, ... makes more sense, please tell it. Sorry that I kept the topic that general. But I hope that the answers will also be useful for others, so I don't like to distract them with my specific problem domain. -- >>>>>>>>>> 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.
