Hi community, For now, whenever default constructor of ExecutorFilter is called, new instance of Executor is created. This often confuses beginners because they see inifinitely increasing number of threads. I admit that I made a mistake due to my lack of knowledge on java.util.concurrent package. (What a lazy...! :) Using Executors.newCachedThreadPool() could fix this problem very easily.
I'd like to apply this change to both 1.x and 2.x branch because it will reduce users' misinterpretation significaly. WDYT? Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
