>Pier / Henri - Care to summerise the tomcat 5 flamewars and other stuff >there? or maybe find someone else to do so? I don't have the >time to look >into it myself so if its gonna go in then someone else needs >to write it.
I'll try to summarise and Pier will make the necessary comments. The TOMCAT 5.0 proposal was launched by Remy. The goal was to design the next generation Tomcat, using the best parts of Tomcat 3.3 and 4.x, using an improved version of coyote (2.0) code as core, and using catalina 2.0 as servlet container. The great thing in that proposal is that members from the 2 olds teams, 3.3 and 4.x agreed on contributing and working together putting the best they learn from 3.3/4.x. There was a proposal from the Avalon team to use Avalon as core, but it was rejected by Remy, who prefer to have something more suitable and lighter for the TOMCAT core. Pier then ask for a Tomcat HA (High Availability), arguing that Tomcat 4.x (he didn't speak about 3.2 or 3.3) was too unstable so it couldn't use it in its production site. There was then a lengthy discussion about stability which should be a major goal and so on. Many people (tomcat-dev) reported having no problems with Tomcat 4.0 or 3.3. To note, the thread was conducted at the same times that many of us make extensive tests on mod_jk 1.2.0 and sus make huge tests on the connector with Apache 1.3/2.0 and Tomcat 3.3/4.0.4 to detect failure in the connector (or in tomcat), and it appears that there was no major problems with both 3.3/4.0.4. As some writers commented, the stability of a web application, depends on many parts, tomcat being one of them, the real java application and remote side (SQL/enterprise applications) being also mandatory. To summarise, I could say that all of us (tomcat developpers) want to have the stablest engine possible and the thread is open. Nota, that the latest proposal is in tomcat4-head : <snipet> The major goals for Apache Tomcat 5.0 are to: - improve scalability, reliability and performance over previous versions - have simpler/cleaner code, so more people can get involved - merge of the various ideas in 3.x and 4.x - get the community togheter - provide maximum modularity and compliance to the standards - make it easy to continue to maintain the existing codebases </snipet> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
