Hi Patrik, Sure and if that is how akka-persistence stays, that is what we will end up doing. But since persistence was marked as experimental, and it was stated that it will changed based on community feedback, I thought I would mention this feature that seems useful and powerful to me and hope others will think so as well.
The difference between having an actor that will then query a bunch of views and an actor that encapsulates all the the logic needed to get a true view of what the business needs to show is exactly that. Think of it as a viewmodel, like you would have in an MVVM app. But, as you pointed out, just like many things in development, there are workarounds. -- >>>>>>>>>> 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.
