Latest NNTP Server is broken but the earlier ones work. For instance I tried James v2.0a2 and that works fine.
These are at least some of the regressions I have found in NNTP changes in 2.1 cycle. These were fixed (all after I found the problems and some after I posted fixes). - NNTP Server not starting at all because of exceptions. - Broken MODE READER command. This is the first command sent by news readers so can't understand how this was missed in any testing. - NNTP Stores should be under apps, now they are created under root directory. - Ability to trace nntp commands was removed. - Authentication was done against repository for Each NNTP Command in a User Session not once per session. Would the responsible developer fix and test NNTP. I could fix this, however this has been some of my experience. - I had reported regressions and posted fixes for at least some of issues. I had also mentioned that I was working on tests before committing the fixes. This was quickly followed by preemptive and untested checkins and bout of name calling. - Could not understand why some of the changes have been done. No clear consensus sought, opinions ignored and outright aggression. - Attempt has been made to actively discourage the developer of nttp server(me). The main justification was a bug that was not closed in 9 months. This bug was verified and could not be reproduced 2 days after it was filed. Bug would show up in a multi-threaded environment and my test was single user test. This is the NNTP Auth Service Bug. Service was stateful not stateless. That was the only open bug. The protocol server was tested with Outlook Express, netscape mail and KMail and users have been able to use the protocol server. This discouragment is by the same developer who has caused all the regressions, not contributed any tests and complained about lack of participation. I will wait for at least a couple of days and fix this issue with tests. Can wait longer is someone request me to. I did know about this a little before Christmas, but - I wanted to upgrade to the latest build - Verify some more and - Let Christmas pass. It was an unpleasant surprise to me and did not really feel like sharing it at that time. I am not interested in nit picking but I do want to say 3 things. - I don't care how nntp is fixed but I would like it fixed. For all I care, fix NNTP(whoever has broken it) and remove my name from author tag. - Alternatively, get out of my way and let me fix NNTP. It should not take long. My estimate is new year or latest first week of January if I start after a couple of days. My preference is that I don't fix things that others have broken(esp. at this time of the year), but I will be happy to take the time and fix this if need be. - I don't think the interaction has been good, but life is too full for negetive thoughts. Let us get this issue fixed before 2.1 is released and move on to more exciting things. thanks, Harmeet -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
