Hello, problems using a view for multiple processors have been discussed before, e.g.: https://groups.google.com/d/msg/akka-user/Tb1Qqh4ZMmo/ssqiBEQ_Eb0J It would still be a great feature to have though(when you need an aggregated view on events of multiple processors). The solution to send the events from views to an aggregator still leaves me with the question why then use a view at all and not just send the events from the processor to the aggregator directly? When using a view in the "middle" one has to deal again with not sending duplicate messages to the aggregator when views replay, persistence(if needed) of the aggregator, losing messages etc. or am I missing smthg?
michael On Monday, 14 April 2014 16:42:08 UTC+2, Chanan Braunstein wrote: > > Entered: https://github.com/akka/akka/issues/15004 >> >> -- >>>>>>>>>> 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.
