[reporter="jvs", created="Wed, 28 Jun 2006 16:27:18 -0500 (GMT-05:00)"]
For example, connections may time out, lying in wait for the next unfortunate soul who comes along and tries to use them. For JDBC, there are existing reliable solutions for this such as
However, we need a general solution, not just for the JDBC wrapper. And there are other issues associated with connection pooling; this is just one example. At a minimum, we should study DBCP to see what problems they solve. Beyond that, maybe there's some other way to achieve reuse, like making wrapper extend Driver and server extend Connection, and providing ways to translate from wrapper-specific errors (e.g. timeout) to errors that DBCP would know what to do with?
[author="jvs", created="Tue, 17 Jun 2008 22:09:10 -0500 (GMT-05:00)"]
For JDBC connections, would also be nice to be able to load up data sources via JNDI.
[reporter="jvs", created="Wed, 28 Jun 2006 16:27:18 -0500 (GMT-05:00)"] For example, connections may time out, lying in wait for the next unfortunate soul who comes along and tries to use them. For JDBC, there are existing reliable solutions for this such as
http://jakarta.apache.org/commons/dbcp
However, we need a general solution, not just for the JDBC wrapper. And there are other issues associated with connection pooling; this is just one example. At a minimum, we should study DBCP to see what problems they solve. Beyond that, maybe there's some other way to achieve reuse, like making wrapper extend Driver and server extend Connection, and providing ways to translate from wrapper-specific errors (e.g. timeout) to errors that DBCP would know what to do with?