Re: Changing the default Executor to Executors.newCachedThreadPool()

[peter royal]

On Jan 27, 2007, at 7:02 PM, Trustin Lee wrote:

For now, whenever default constructor of ExecutorFilter is called, new

due to my lack of knowledge on java.util.concurrent package. (What a

very easily.


reduce users' misinterpretation significaly.  WDYT?

instance of Executor is created. This often confuses beginners because they see inifinitely increasing number of threads. I admit that I made a mistake lazy...! :) Using Executors.newCachedThreadPool() could fix this problem I'd like to apply this change to both 1.x and 2.x branch because it will

You mean replacing:



?



-pete

--
[EMAIL PROTECTED] - http://fotap.org/~osi

new ThreadPoolExecutor(16, 16, 60, TimeUnit.SECONDS, new LinkedBlockingQueue() ) (if so, that's roughly equivalent with what newCachedThreadPool does, just different numbers, which makes me wonder why :)

smime.p7s
Description: S/MIME cryptographic signature