On Mon, Feb 20, 2017 at 5:55 PM, Jim Jagielski <j...@jagunet.com> wrote: > >> >> It could be done, but who would use it that way? >> > > I think the non-thread safety of pools requires that each > person/developer implement their own locking esp around areas > where they might not even understand that there is cross-thread > issues. Thinking about 1.6 and especially apr 2.0, it makes > one wonder when/if we should bite the bullet and add thread > safe pools in a canon and supported and opaque way instead of > the normal "hacks" around it...
That'd be for the "garbage collector" functionality of pools, not necessarily in a performance critical environment (where usually the headaches come from :) >
