These are chat archives for petabridge/akka-bootcamp

Aug 2016
Jon Blackburn
Aug 28 2016 19:44
In module 2.4 you present Become/BecomeStacked, presenting authentication as an example of a use case for changing an Actor's behavior using BecomeStacked. Authentication is a cross-cutting concern and shouldn't be coded into your business logic like this. I'd expect it to be applied in some sort of decorator pattern implementation. What kind of facility does Akka provide to enforce AuthN/AuthZ (or other cross-cutting policies) using composition/interception, as opposed to making every one of my Actors aware of the need?