commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simone Tripodi <simone.trip...@gmail.com>
Subject Re: [pool][dbcp] cross pollination
Date Mon, 18 Oct 2010 14:44:58 GMT
Hi all,
even if as developer was involved I recently, in therms of APIs, as
user, I'd prefeer keeping the 2 things separated:

 * the pool is a set of APIs with interfaces and some concrete
implementations to create generic pools; i.e. I used it to pool
instances of commons-digester parsers or httpclient instances;

 * the DBCP is a specific DatSource pool.

I wouldn't like adding a generic pool library that brings the JDBC
connection pooling stuff, IMHO it continues making sense keeping the 2
separated.
Just my 2 cents,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Mon, Oct 18, 2010 at 3:38 PM, Paul Benedict <pbenedict@apache.org> wrote:
> Has any thought been given to simply rolling the projects into one?
>
> On Sun, Oct 17, 2010 at 2:13 PM, Phil Steitz <phil.steitz@gmail.com> wrote:
>> On 10/17/10 2:58 PM, Gary Gregory wrote:
>>>
>>> Shouldnt we talk more across these two projects? Perhaps making sure we
>>> have good reuse and cross pollination
>>
>> Commons is *one* project.  That said, the answer is obviously yes. As we
>> start to bring in the jdbc-pool stuff, this will become even more apparent.
>>  Coordination between [pool] and [dbcp] has never been an issue in the past
>> and I don't see that changing now.  Often fixing issues in [dbcp] ends up
>> leading to [pool], so there has always been a lot of overlap in contributors
>> to these two.
>>
>> Phil
>>>
>>> Gary
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>>> For additional commands, e-mail: dev-help@commons.apache.org
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message