commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: DBCP status?
Date Mon, 23 Jun 2003 17:28:55 GMT

Howdy,

>Since James really does need a new connection pooler, and I'm stuck
>having to invest some time into making **some** database pooler more
>robust, is the DBCP project open to this?  I'm not sure if there are
any

I'm positive no one would oppose you contributing and working on it ;)

>- Allow the pool to optionally close a connection on a SQL exception
>(since that will often corrupt the transaction and/or indicate the
>connection is boofed).
>- Change some default values so it doesn't block indefinitely to open a
>connection out of the box.
>- Maybe support a connection factory constructor that can take a String
>for a driver name, rather than require you to do Class.forName()
>separately.
>- Maybe implement login timeout.
>- Maybe implement logging via commons logging so you can catch events
>rather than just use a writer.
>- Make a formal new release (either 1.1 or 2.0, I don't care), just so
>the examples, test code, and javadoc (in distro and website) all have
>working examples.

The above ideas all seem cool to various degrees.  I dislike the
commons-logging one, as that may cause some problems for people using
DBCP who don't want to use commons-logging.  But testing can iron that
out and I don't think it'll be a showstopper ultimately.

>Any feedback on these changes, or people I should talk to before
heading
>down this road?

You already have the above list; I would start by entering them as DBCP
enhancement requests in bugzilla.  Then start working them and send in
patches to the mailing list (appropriately marking the subject lines,
i.e. [DBCP][PATCH]).  The committers will comment...

Yoav Shapira



This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


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


Mime
View raw message