Noel J. Bergman wrote:
Serge,
Not sure what is running on nagoya, but Brian had indicated that he'd like
to be able to run James on FreeBSD, and I don't know when JDK 1.4 will be on
that platform.
Yeah, I think that may be the overiding factor as if we want Apache to
use James and they're running FreeBSD without 1.4. doh!
- JNDI DNS Service
Not sure how much this practically buys us. Your thoughts? Can we make use
of this optionally?
Yes, during initialization you can specify what DNS servers to use. If
there aren't any specified, for < 1.4.1 it defaults to localhost. For
>= 1.4.1, it uses your underlying DNS settings (like /etc/resolv.conf
or Windows XP network settings).
- JDBC v3
The primary benefit we want is pooling, for which we can use DBCP, but I
think we should make sure that someone with JDK 1.4 can substitute JDBC v3
transparently, so we have to be careful about what interfaces we expose.
Ok, I don't know how you expose it transparently, but we can see. Maybe
offer DBCP as a wrapper so you could alternatively just specify your
own. Is this really such a big deal? Right now we don't offer any
pooling alternatives (and the one we offer isn't as good).
- Better networking
We can do without it for now.
I haven't done the cross-JDK version stuff in a bit, but 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).
- java.nio (too bad NBIO isn't more portable; we should look a SEDA,
too)
Since java.nio doesn't support TLS, yet, we can't use it anyway. But we
should design the handlers as if we were using non-blocking I/O, even though
we don't switch yet.
Well, Peter and others have much expertise and recent experience working
on the handlers, so if Peter or however else can rework to support
future non-blocking IO, I guess that's nice.
So perhaps we can stay with JDK 1.3, but I think that we ought to keep an
eye on where things are going, and allow such things as replacing DBCP with
JDBC v3 transparently.
Def.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
