These are chat archives for petabridge/akka-bootcamp

30th
Aug 2016
Jon Blackburn
@jeblackburn
Aug 30 2016 02:28

Thanks, @Aaronontheweb. If, as you say, Auth*n isn't considered to be a responsibility of Akka's, maybe the tutorial could be changed not to present it as a use case? One could extend the chat client example with a "Do Not Disturb" feature that is both business logic and Stackable behavior.

Am I to understand that there are no AOP hooks in Akka.Net? I was expecting to hear that one could decorate an Actor directly with something like a Python decorator, or override a Dispatcher method to enforce an Auth*n policy at a point a couple of frames up the stack from the Actor. Does that make sense? If I'm looking for something that's really not there, I'll have to rethink some things.

Thanks again.

Aaron Stannard
@Aaronontheweb
Aug 30 2016 16:37
@jeblackburn it's just an example that everyone can relate to
there are some AOP hooks in Akka.NET - best place to do it is via an actor base class
you can override AroundReceive to instrument monitoring on all actors using that base class, for instance
we also have the notion of ActorSystem extensions
which is how Akka.Cluster, Akka.Persistence, and Dependency Injection are instrumented
Jon Blackburn
@jeblackburn
Aug 30 2016 17:48
@Aaronontheweb Thanks, I'll look at AroundReceive as an option.
Aaron Stannard
@Aaronontheweb
Aug 30 2016 23:18
you're welcome!