on 12/26/2000 1:42 PM, "Marcelo Vanzin" <[EMAIL PROTECTED]> wrote:
>> You are missing the ability to get the age of a java.sql.Connection. That is
>> important for a pool given that we want to be able to expire Connections
>> based on age and is the primary reason for the DBConnection class.
>
> I don't see how implementing the interface would change that... I'm not
> saying to use the java.sql.Connection interface throughout Turbine, that
> surely would break the pool system, I was thinking about a class lib
> made by someone else who was not developing it for use with Turbine.
Because DBConnection isn't a java.sql.Connection. It is a wrapper object
around a java.sql.Connection.
> Anyway, the getConnection() method does just what I was thinking about
> (although I don't like the idea of giving the real connection to the
> classes, a misplaced close() there would not be a good thing), so,
> that's ok.
You should never attempt to close() a Connection while using a Connection
pool. That is just plain bad. :-)
Anyway, if you are using the Peer system (which you should be), then all of
this is moot anyway since it handles this under the covers.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
