Hi Muki, I like the pattern. In details I would use it a bit different though. I do not like that some of the logic is hidden in the trait, I would prefer only to pass the messages to typed receive methods in greetingReceive.
It does not add any real typesafety though, as there is no way to ensure that the actor passed into your consumer actually meets the contract, therefore I would not really see it as an alternative to typed actors, but as a way to document and enforce the contracts between two actors. The wiring of the actors still can go wrong and is not enforced in any way. Still, I think this is a worthwhile pattern especially when facing developers new to Akka or very complex actor wiring. I would love to see an Activator Template with a more complex example using this pattern. Cheers, Michael Am Donnerstag, 31. Juli 2014 00:06:02 UTC+2 schrieb Muki: > > Hi, > > I created a small sample app for a little architecture pattern for akka > applications. > The idea can be terribly wrong, but I wanted to get some feedback on it: > > https://github.com/muuki88/akka-architecture > > > The README explains the pattern and how to apply it. It's more or less a > way > around typed actors. > > cheers, > Muki > > -- >>>>>>>>>> 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.
