From: | Aaron Mulder <ammulder(at)alumni(dot)princeton(dot)edu> |
---|---|
To: | PostgreSQL JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Adding JDK1.5 removing 1.1 support. |
Date: | 2004-07-16 12:50:59 |
Message-ID: | Pine.LNX.4.58.0407160845130.13007@saturn.opentools.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Fri, 16 Jul 2004, Oliver Jowett wrote:
> I'm actually tempted to drop the pooling DataSource implementations
> altogther. Does anyone on the list actually use these? I think the more
> common approach is for a higher layer to use our
> ConnectionPoolDataSource implementation (or plain DataSource, even) plus
> their own pooling logic..
The spec seems to have been originally written so that any
middleware should use ConnectionPoolDataSource. In practice, that seems
pretty rare -- every app server I've worked with uses an XADataSource or
DriverManager. On the other hand, most end users don't seem to know what
to make of a ConnectionPoolDataSource, since it's neither a DataSource nor
a Connection, and they don't want to implement their own pooling logic.
So if we were to drop support for anything but ConnectionPoolDataSource,
then I'm not sure that anyone would really use this stuff at all!
That said, it's hardly a scientific opinion, and I would also be
interested to hear if anyone speaks up and indicates that they're using
ConnectionPoolDataSource.
Aaron
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Smith | 2004-07-16 13:40:21 | Re: Adding JDK1.5 removing 1.1 support. |
Previous Message | Stefano Bonnin | 2004-07-16 11:17:47 | Re: SSL Problem |