the dispatching infrastructure in Akka.NET basically queues up groups of actors for processing
and can dispatch actors to work across an arbitrary number of threads
but one actor can only work on one thread at a time
if the actor still has unprocessed messages in its mailbox once it's finished
if you stick with what gets exposed via
ActorContext
or whatever the
Context interface is
that's all of the stable parts of the Cell API
and exposes everything you care about
most of what the
ActorCell does internally is stuff like managing child actors
and handling deathwatch
etc
albeit, it's unsafe
but it's public API
this is the
ThreadStatic variable I mentioned earlier
we have a more safe way of exposing that somewhere
I don't remember where it is off the type of my head
but if you're curious about the internals, the
ActorCell stuff is really at the heart of the actors
enjoy your stay and let us know what we can do to help you :p
How about the tardigrade? Very resilient. Even to the conditions of space.
Or what about the honey badger?
you can do a full akka.remote actor selection
actor hierarchy -S akka.tcp://MySys@127.0.0.1:4053
that'll query the actor hierarchy of the remote node
@nathvi lol a honey badger mascot
I like it
I'd also take something weird too
