remm 2002/06/24 09:48:29
Modified: . PROPOSAL-5.0.txt
Log:
- Add details about the changes which will be introduced over the current
Tomcat codebase.
Revision Changes Path
1.2 +55 -1 jakarta-tomcat-4.0/PROPOSAL-5.0.txt
Index: PROPOSAL-5.0.txt
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/PROPOSAL-5.0.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- PROPOSAL-5.0.txt 21 Jun 2002 10:41:18 -0000 1.1
+++ PROPOSAL-5.0.txt 24 Jun 2002 16:48:29 -0000 1.2
@@ -18,6 +18,7 @@
Process.
The major goals for Apache Tomcat 5.0 are to:
+- improve scalability and reliability 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
@@ -65,7 +66,7 @@
Apache Tomcat 5.0 will be made by default of the following components:
- Coyote 2.0 - core
- Catalina 2.0 - Servlet API 2.4 implementation
-- Jasper 3 - JSP 2.0 implementation
+- Jasper 2 - JSP 2.0 implementation
Many other configurations are also possible, and it is expected that advanced
users take advantage of it to make Tomcat better suit their needs. It is also
@@ -74,6 +75,59 @@
Due to the scope of this work, this initial Proposal only plans
the implementation and support of the default configuration described above.
+
+
+
+Changes over Apache Tomcat 4.1.x:
+--------------------------------
+
+
+A lot of the Apache Tomcat 5.0 code will be based on the Apache Tomcat 4.1.x
+codebase. Tomcat 5.0 will also be able to use the Tomcat 3.3.x code.
+
+The following major changes and additions are proposed to the current Apche
+Tomcat code, and related dependencies:
+
+A) Removal of the org.apache.catalina.connector.*
+
+This package is currently deprecated in Tomcat 4.1 because of
+its implementation inefficiencies, and general bad design. It is thus proposed
+that it is removed in Tomcat 5.0.
+
+B) Addition of new loader code for the commons-daemon subproject
+
+It is proposed that, in an attempt to solve the problems with using startup
+scripts, as well as adding additional features oriented towards reliability
+(including the capability to restart Tomcat automatically should the JVM
+crashes or experience memory management related problems), the launcher code
+which will be developed as part of commons-daemon be adopted.
+This code will be based in part on the launcher code used for the Sun Web
+Services Pack, and in part on the Wrapper project code (available at SF.net),
+if we manage to come to an agreement with the Wrapper developers.
+
+C) Extensions to Coyote
+
+It is proposed that Coyote 2.0 include the following changes over Coyote 1.0:
+- The current hook mechanism used in Coyote 1.0 will be extended to be
+more generic and powerful.
+- It is also envisioned that JMX management capabilities could be added
+to Coyote.
+- Deprecated interfaces will be removed (two interfaces, at the moment).
+- An additional protocol handler for the WARP 1.0 protocol will be added
+provided there is user interest and developers willing to dedicate time.
+
+D) Implementation of the Servlet 2.4 Specification
+
+Catalina 2.0 is proposed to be identical to Catalina 1.1 (included
+in Tomcat 4.1.x), with the exception of adding support for the new Servlet
+Specification. The changes introduced in this new revision are relatively
+limited, and shouldn't cause any major architectural changes in Catalina.
+Catalina 2.0 will also inherit from all the refactorings done in Catalina 1.1.
+
+E) Implementation of the JSP 2.0 Specification
+
+Jasper 2 will be modified to support the new JSP Specification. More important
+changes will be required than for supporting the new Servlet Specification.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
