Noel J. Bergman wrote:
You talked about exposing javax.sql.DataSource.
Right, that's how I propose offering db connections to anyone (the only way instead of the Avalon lookup to the mordred pool).

> Another question is whether
we need to offer a pool directly, or whether we just need to provide the
means to get a suitable (pooled) connection?
I think just a pooled connection is enough. Maybe for monitoring you'd want the actual pool, but dunno why else you'd want the pool directly. Thoughts?

ideally we could use the better exceptions in JDK 1.4 to build richer
failure

messages, but if they're not available, then just skip them and do what
we do now. (also similarly if the extra socket options are available,
then set them, otherwise ignore them).

How do you propose coding that?
I'm not sure... possibly reflection? Again I haven't done the cross-JVM version coding in a bit, so I'm rusty on how you would go about doing this.

--
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to