Is it good practice to change the processorId on a View to support replaying messages from multiple sources?
I currently have an aggregator view that instantiates new child views in response to user registrations. These child views then propagate messages back up to the parent aggregator view. I've seen this pattern advocated in previous topics, but it got me wondering: why not just change the current view's processorId and avoid instantiating new child actors altogether? -- >>>>>>>>>> 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.
