For what it's worth, we use a homemade solution for this problem. It looks quite a lot like one described in an answer to your stackoverflow question (but with a bit of sugar on top). Basically we allow a future to be marked as "local" which will cause all its callbacks to be executed via the normal message handling of the defining actor, but without having to move the callback handling code out of the future callback and into a message handler. This has worked out quite well in practice, but Rolands observations still stand of course. You can find the code at: https://gist.github.com/odd/e356e178bfa178f727e3
Greetings Odd -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
