Le 7/1/13 11:08 AM, Zlatko Josic a écrit : > Hi Emmanuel, > > So if I have tasks that access database and communicate to external systems > it is good to have solution that I have described in the previous post? > > Also I have found that some of external systems sometimes have timeouts in > communication so this is an argument for own thread pool. > Actually I can have separated thread pool for those system so timeouts will > not > impact rest of system so much which will be in case if I use > ExecutorFilter. I guess.
If you want more control, then it makes sense to declare your own threads. It's a good policy to delegate to your own thread a message you just received, to free the thread that processed the read. You own thread can still write as soon as it know about the session. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
