> I think that may be the overiding factor as if we want Apache to
> use James and they're running FreeBSD without 1.4.
Yes, right now it is FreeBSD 1.3.1, Classic VM, green threads, no JIT. I
understand that there is a JIT available for FreeBSD, though.
> right now we don't offer any pooling alternatives
> (and the one we offer isn't as good).
You talked about exposing javax.sql.DataSource. 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?
> 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?
> can rework to support future non-blocking IO
Typically, you just need to invert the handling so that data is pushed into
the actual protocol handler, instead of being pulled. In most cases, we're
pretty close.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
