tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: [5.next] Summary
Date Fri, 11 Jun 2004 17:26:04 GMT

Hi,
Cool stuff ;)

I'm away in two weeks, so I'll tag and branch 5.0.27 and TOMCAT_5_0 at the end of next week,
so that you can start working on HEAD two weeks when you're back from vaca.

Yoav Shapira
Millennium Research Informatics


>-----Original Message-----
>From: Remy Maucherat [mailto:remm@apache.org]
>Sent: Friday, June 11, 2004 12:51 PM
>To: Tomcat Developers List
>Subject: [5.next] Summary
>
>- Move to concrete classes for request/response, and remove all of the
>RTTI done in Catalina's pipeline
>- Use Tomcat 4.0 beta valve pattern
>- Redo logging using commons-logging, and remove Logger
>- "Fork" commons-digester, to remove what we don't need (many fancy
>features provided by beanutils, and in the process remove dependencies
>on beanutils and collections)
>- Attempt to redo a bit the deployer:
>   * remove the CL code which is there to avoid JAR locking (or at least
>allow disabling this feature for non-Windows OSes)
>   * move processing of context.xml to ContextConfig (at the expense of
>being able to specify the context class, which will move to an attribute
>on the Host), as I realize it is important to get context level
>configurability without adding too much complexity in the embedding
>application
>- Use the webapp CL as the main CL (without the locking tricks it is
>likely faster than the regular CL)
>- And the ongoing: allow all config/management through JMX (actually, we
>could consider going to a JMX config format)
>- Use any means necessary (hehe) so that Filip refactors the clutering
>module, and extend the regular Catalina objects, for easier maintenance
>- Remove anything useless (spring cleaning time), such as configuration
>options, container listeners (to be replaced with JMX notifications
>where it matters), etc
>- Possibly require JDK 1.5 (cleaner code, annotations, integrated JMX
>and JMX remote, etc)
>
>Overall, the throughtput of Tomcat should go up about 5-10% with those
>changes, as most significant optimizations are already done.
>
>I don't think any of these items will take too long to implement. I'm
>away next week, so I'll start the week after.
>Some of this could eventually be backported to 5.0.x :)
>
>Rémy
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org




This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message