DB Connection Pool [was: some cool hacking projects...]

[James House <ho...@spectre.com>]

-- Is this something that would be beneficial for inclusion in the
Jakarta project?

I'd be willing to APL it if people desire it...

>I have made a connection pool package where the main class just
>implements the java.sql.Driver interface thus eliminating the need
>for a standard 'ConnectionPool interface'
>
>When you ask the driver for a connection (the connect() function)
>it goes and asks the pool for one, and returns it to you, when you
>are done with the connection (close()) it returns it to the pool (without
>physically closing the connection),  etc. etc.
>
>I think this is a logical way to implement a connection pool, so that
>it is seamless with JDBC.
>
>It's yours for the asking...
>
>
>At 12:18 PM 10/15/99 +0100, you wrote:
>>"Anil K. Vijendran" wrote:
>>
>>An area of concern with servlets like this is the number of supporting
>>classes that make them harder to reuse elsewhere. For example we use a
>>ConnectionPool, but there are many around and really we want to make
>>these pluggable (so we use a ConnectionPool interface, but no doubt
>>other connection pools currently have different interfaces).