Alan,
> With the current James JDBC functionality, what will we explicitly gain by
> implementing this driver ??
I'm just planning ahead. The v3 driver is still in beta, but ought to be
suitable for improved JDBC access in James v3. Even if the new driver had
some critical bug fixes over the current driver, I'd just as soon re-do the
bug fixes (generally an easy thing to do once you know that a bug exists)
for James v2.1.
In any event, API enhancements aside, the new driver has improved
performance and memory consumption characteristics.
--- Noel
--
To unsubscribe, e-mail: <mailto:james-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@;jakarta.apache.org>
