For the moment but the long-term strategy would be to move everything to use block directly rather than ThreadContext.getThreadPool(). The main reason is because that matches how we use it and it would be easier to manage performance characteristerics of pool that way.
I'm intrigued. You see multiple implementations of threadpool don't you..
-PH
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
