Matt,
I appreciate your view, but also please note that the feature matrix on the
bottom of the page lists NNTP as experimental.
Also, you should be aware that NNTP was broken in 2.0a3. Just in different
ways. There are reasons why the code was changed in the first place.
Another thing is that you are accepting Harmeet's allegations regarding the
person who made those changes. What you don't realize is that you are
getting in the middle of a conflict where the original author of the code,
Harmeet, has made it clear in prior discussions dating back to October that
he wasn't happy to have changes made without his consent. He had been
absent from the Community for the better part of a year, and only came back
when those changes were made.
Incompatibility with OE and other newsreaders is indeed a show stopper for
that protocol, but an experimental protocol is not a show stopper for James.
NNTP hasn't been taken as seriously hitherto, and is not a core protocol.
That should change, but it does not need to hold up release of what are the
core protocols today. Also, we really don't know yet what the issues are.
The current patch, which may fix some issues, is a simply print statement.
Cnce we ship v2.1, with the previously posted patch for NNTP and NNTP
disabled (it is simply a config.xml setting that anyone can toggle), then we
can apply other fixes and release a v2.1.1. Consider the Tomcat 4.1 is
currently passed v4.1.18. They release often, as shall we after this point.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
