On 13.09.2010 23:17, William A. Rowe Jr. wrote:
On 9/13/2010 4:15 PM, William A. Rowe Jr. wrote:
On 3/1/2010 4:45 AM, Mladen Turk wrote:
The Apache Tomcat team announces the immediate availability of
Apache Tomcat Connectors 1.2.30 stable.
With this release, following the retirement of httpd-1.3 from all maintenance,
would this be a good time to declare this the final native/apache-1.3/ connector
and remove that tree from svn at this point, prior to any 1.3.31 release?
I meant, prior to any 1.*2*.31 connector release
I don't have any problem of freezing the 1.3 support concerning features
and minor bugs, but I find it a bit surprising for users to suddenly
stop supporting 1.3. In my opinion we should still do security fixes
when needed and critical bugs. Most os the time the 1.3 support is
cheap, because fixes or enhanceents are in the common code.
So telling users now, that we only plan to do security fixes on the 1.3
support would be OK for me.
I think that mod_jk 1.2 (all web servers) should stay pretty stable now
w.r.t features and it would make more sense to start 1.3
- with reasonable default values for all of those timeouts etc. that
have been added over time and which are all of by default
- with adding some probing to the watchdog thread
- I would like to add saving of changes done via the status worker
- and dropping support for Apche 1.3 and likely also NSAPI
I have the impression there is not enough dev time available at the
moment for bigger things like migrating it to APR, but a switch to 1.3
would allow us to formulate a clear message (some incompatibilities,
partially dropped support and a couple of new features).
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
