"Long running" handlers

[infectedrhytms]

Ok the MemoryAwareThreadPoolExecutor seems to do the trick. Thanks I think I
may right up a simple example cause there is now way I would have figured
this out.

Just to be clear. Cause I'm still trying to gasp this Chanels, Events etc...
thing...

With MemoryAwareThreadPoolExecutor will any event fired off in one instance
of MyBusinessHandler() affect the instance of another one. So if I have 3
threads running 3 separate instances of MyBusinessHandler, what ever happens
in one will not affect the other right, only the order of the execution may
not be the same which is fine because who ever finishes faster the better?

So for instance a close event in 1 BusinessHandler will not affect the other
2?
-- 
View this message in context: http://n2.nabble.com/Long-running-handlers-tp4677280p4686961.html
Sent from the Netty User Group mailing list archive at Nabble.com.