HiGary, I agree on your point of view, I wonder if we can even create abstract classes for common settings to avoid redundancies, I don't know if it could make sense. Have a nice day! Simo
http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Sat, Oct 30, 2010 at 6:56 AM, Gary Gregory <ggreg...@seagullsoftware.com> wrote: > In [POOL-178] I have created a patch that IMO should make it easier for us to > further refactor code. > > > > In brief, OP/BOP and KOP/BKOP do not have a common parent interface/class. > This patch remedies this by pulling up the > close/clear/getNumActive/getNumIdle methods into a new interface and class. > > > > This seems not very controversial (to me at least), so I would like to commit > it (unless riots spread from Paris to this list.) > > > > Thoughts? > > > > [POOL-178] https://issues.apache.org/jira/browse/POOL-178 > > > > Gary Gregory > > Senior Software Engineer > > Rocket Software > > 3340 Peachtree Road, Suite 820 * Atlanta, GA 30326 * USA > > Tel: +1.404.760.1560 > > Email: ggreg...@seagullsoftware.com > > Web: seagull.rocketsoftware.com > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
