First off, is anyone working on Connection pooling (specifically JDBC connection pooling?) If not, I'd like to get started working on that.
Just to make sure that I'm on the right track, here's what I'm thinking: (sorry, copied from IRC chat.)
I would just have to create a service, that on startup (depending to the server config) creates connections to a JDBC client
and keeps a few of those open, acting something like a FactoryObject and parseling those out to apps that need them
all the while keeping a minimum open to the JDBC datasource
and possibly not letting them go too long.
This is a possible approach.
Another one, and I think it is the preferred one, is to implement a JDBC Connector. The goal is to re-use the J2EECA architecture, which explicitely defines the security, the transaction, the logging et cetera of (Managed)Connection.
Hopefully, it should be able to leverage a significant part of the Connector implementation by implementing such an adaptor for JDBC drivers.
Cheers, Gianny
_________________________________________________________________
MSN Messenger http://g.msn.fr/FR1001/866 : un logiciel gratuit pour dialoguer avec vos amis !
