>> If anyone is strongly bothered by ObjectPool.numIdle() and >> ObjectPool.numActive() versus the getXXX() style, now might be the right >> time to change it, although it may already be too late depending upon how >> broadly pool is being used. >>
> How about adding getXxx() versions, implement the old ones in terms of > them, and deprecate the old ones? If we add getActiveCount()/getIdleCount() methods to the interface, it'll break any custom implementations of ObjectPool that are out there. (This is of course why I want to add the base impls, then it'll only break anyone who's implementing ObjectPool directly.) I'd lean toward doing this now rather than for a 2.0 release. I'm not even aware of anyone using a custom ObjectPool impl, but this'll surely find them.
