> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 20, 2001 1:03 AM
> To: Turbine
> Subject: ConnectionPool ammendemends: JDBC 2.0 Compatibility & More
> (2/2)

[SNIPPED]
> Also,
> to be absolutely honest, the way that DBConnection is used is 
> not quite
> right. I would prefer
> a re-write of the ConnectionPool+DBConnection classes in 
> order to actually
> make use of
> all the JDBC2.0 extenstions (Use PooledConnection, 
> DataSources, etc) and use
> correctly
> the new interfaces (this can actually be done without 
> breaking existing
> compatibility).
[SNIPPED]

I'm +1 with you on the above.  While I don't have time to implement this
now, I may have time to test changes posted to CVS with our current
applications.  Not breaking existing applications/peers and moving to the
sun interfaces would be great.  There has been some talk on jakarta-general
about this and basically, no one has had the itch yet.  Go for it.

jb


-----------------------------------------------------------------------

This message has been scanned for viruses with Trend Micro's Interscan VirusWall.


------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?:           [EMAIL PROTECTED]

Reply via email to