Craig,
I'm willing to volunteer my time and effort to help out with maintenance of
3.x. We are embedding Tomcat 3.2.x into our product so I have a vested
interest in making sure that the 3.2.x product is stable and robust.
I've submitted a few patches in the last month or so (and gotten a couple
accepted and committed). I've also been actively trying to help people on
TOMCAT-USER with problems related to IIS integration and the
isapi_redirector as these are the areas that I've focused on most.
There are currently a few items left in 3.2.x that I'd like to address:
1) The long delay required to initialize SecureRandom causes the first
access to a web app to take a significant amount of time. I posted a patch
to address this but I admit that it touches a few more classes then I would
have liked. If anyone has other ideas or comments I'd like to hear them.
2) The EmbededTomcat class doesn't work at all. I used it as an example to
develop my own and I'd like to merge those changes back into the Tomcat
source.
3) The isapi_redirect.dll is very brittle. Very small and (based on the
questions posted to TOMCAT-USER) very common configuration mistakes cause
failures that are difficult to diagnose.
At some point I want to look into Tomcat 4.x, but for the near future my
focus must be on the 3.2.x product. If I can help maintain this release to
free up other developer's time for 4.x please let me know.
-----Original Message-----
From: Craig R. McClanahan [mailto:[EMAIL PROTECTED]]
Sent: Monday, December 18, 2000 8:01 PM
To: [EMAIL PROTECTED]
Subject: Re: [MY_OPINION] Tomcat 3.x
<snip>
Of course, these problems are fixable if we had more committers ...
especially
ones interested in applying bug fixes to the current production release to
keep
it stable and appropriate for production deployments.
(NOTE: Anyone who receives committer status gets commit access on all
branches
of all the project's CVS repositories.)
<snip>
