For now, there's a strong 1-to-1 relationship between PooledThreadModel and thus it causes excessive creation of thread pools. I think at least the PooledThreadModel instances with the same service name should share the same ThreadPoolFilter insstance. What do you think?
If you agree with me, there are two choices: * Provide a static factory method for PooledThreadModel instead of constructors. * Retain the constructors, but share the filters using a static map. Thanks in advance for your feedback! 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
