Remy Maucherat wrote: > > > - Tomcat 5 is Tomcat 4 with lots of cleanup work and > > modifications for whatever the 2.4 spec comes up > > with. There are no major architectural changes. OTOH, > > the 2.4 spec could be bizarre, in which case all bets > > are off :-) > > My proposal is not very different from that. >
Maybe I'm just hung up on some of the wording, then. I'd like to see specifically: - An item about coming up with a set of benchmarks and performance goals as a priority. My BS alarms go off when people discuss performance outside of an agreed upon set of benchmarks (even if I know them to be smart developers who probably have really done the bencharks and profiling) - Details about how the existing Catalina JXM management interfaces will be merged with Coyote JXM management code. Or at least an acknowledgement that it's an issue. - A listing of specific issues with Tomcat 4's current implementation. for example, the startup code is opaque, it's unclear what events get sent when, etc. The important thing is that there's a specific list of problems that need to be solved. - And (I may be reaching here), Coyote is moved from being "core" to being "the connector architecture". > BTW, maybe you consider all that ugly, but I don't. I find > the XML Mapper / Digester pretty cool > I really like the Digester. I was referring specifically to how non-optional parts of the core implementation (like ContextConfig) are added as listeners instead of being called explicitly. They look like they should be pluggable, but the way they're implemented right now, they're not. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
