1) resume supervisor strategy
2) Make receive final in the general EndpointActor and impl the
try-catch-reply there, and delegate the actual message processing to an
abstract method. That breaks down if using become, but otherwise it's fine.
/Patrik
lör 1 apr. 2017 kl. 21:17 skrev kraythe :
> Th
There are two situations where i need to deal with exceptions outside of
the normal "Let it crash" paradigm.
First is an actor that can't crash. I have some actors that cache a ton of
information and their startup can take quite a while. If some method throws
in the actor unless the exception