Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [5.next] Summary
Date: Fri, 11 Jun 2004 13:26:04 -0400
Message-ID: <9C5166762F311146951505C6790A9CF80229BB09@US-VS1.corp.mpi.com>
Thread-Topic: [5.next] Summary
thread-index: AcRP1CqZ4psT4R1KT92M+AHzzi7UogABOILw
From: "Shapira, Yoav" <Yoav.Shapira@mpi.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>


H=
i,
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 th=
e
>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 dependencie=
s
>on beanutils and collections)
>- Attempt to redo a bit the deployer:
>   * remove the CL code which is there to avoid JAR locking (or at le=
ast
>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 attrib=
ute
>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 cluterin=
g
>module, and extend the regular Catalina objects, for easier maintenan=
ce
>- Remove anything useless (spring cleaning time), such as configurati=
on
>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 thos=
e
>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=E9my
>
>
>---------------------------------------------------------------------=

>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 com=
munication, and may contain information that is confidential, propriet=
ary and/or privileged.  This e-mail is intended only for the individua=
l(s) to whom it is addressed, and may not be saved, copied, printed, d=
isclosed or used by anyone else.  If you are not the(an) intended reci=
pient, 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