Plans to Shift from Current Connection Pool to Another In Next Version

[Hutson Carspecken <hu...@myprivacypolicy.com>]

Noel,

I wrote about the connection pool and have since done a considerable amount of reading on the JDBC API implimentation of connection pools.  Thank you, I was farther behind than I expected.

You mentioned that JAMES is moving to another version of connection pooling.  As I would like to stay in the realm of JAMES as much as possible, could you please elaborate on that future move?  

Hut

RE: Plans to Shift from Current Connection Pool to Another In Next Version

["Noel J. Bergman" <no...@devtech.com>]

A change of connection pool is supposed to be transparent to client code.
There will be a non-transparent change in James v3, but that is simply to
provide the data source via a different mechanism (probably JNDI), instead
of Avalon.

	--- Noel

-----Original Message-----
From: Hutson Carspecken [mailto:hut@myprivacypolicy.com]
Sent: Thursday, July 17, 2003 14:34
To: James Users List
Subject: Plans to Shift from Current Connection Pool to Another In Next
Version


Noel,

I wrote about the connection pool and have since done a considerable amount
of reading on the JDBC API implimentation of connection pools.  Thank you, I
was farther behind than I expected.

You mentioned that JAMES is moving to another version of connection pooling.
As I would like to stay in the realm of JAMES as much as possible, could you
please elaborate on that future move?

Hut


---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org