make Failed a SystemMessage
this is forced upon us by BalancingDispatcher and bounded mailboxes, and then guaranteed delivery of system messages will be reusable
Leave a comment
on 2012-07-12 08:49 *
By viktorklang
I'd rather make it a system message and ride on the "guaranteed delivery" of those.
The solution outlined in #1478 does not cover the case of a Failed being dropped due to a BoundedMailbox. Either we need to make Failed a proper SystemMessage (which will have different ordering semantics in a user-visible way), or we declare BoundedMailboxes to be required to always accept Failed messages. Both are not nice.
on 2013-01-18 05:44 *
By viktorklang
One word: BalancingDispatcher
Made Roland's attempt working: https://github.com/akka/akka/commits/wip-2299-Failed-SysMsg-∂π
There might be possible improvements though, but the tests are at least green.
There might be possible improvements though, but the tests are at least green.
on 2013-03-04 05:45 *
By viktorklang
Awesome!
I think it's also time to clean up the code surrounding SystemMessages, right now it's not really as maintainable as we'd like it to be.
Specifically the "var todo" etc.
I think it's also time to clean up the code surrounding SystemMessages, right now it's not really as maintainable as we'd like it to be.
Specifically the "var todo" etc.
Yes, Endre and I came to the same conclusion: we will spend four more bytes in ActorCell (i.e. move the `todo`) to make it nicer, but not right now (https://www.assembla.com/spaces/akka/tickets/3119)