Following up on my previous post, say there is a careful thread management which interrupts a long running task, I have been there...if you are interrupting something you coded, then probably you will refactor your code so that it doesn't need to be interrupted which leads to another scenario, you are trying to interrupt an alien API, you know that changes of a bad designed API to be interrupted are from slim to none right?
That said, you will have no other choice than to isolate such calls to dedicated dispatchers, it all boils down to two things: 1. Interruption in Java which most of the time you do not have control. 2. Thread scheduler fairness which you also have no control. So I strongly believe the best you can do is to "isolate" or "divide and conquer" Hope that helps, Guido. -- >>>>>>>>>> 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 akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
