You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by rj...@apache.org on 2007/05/08 17:17:02 UTC
svn commit: r536218 - /tomcat/connectors/trunk/jk3/ROADMAP
Author: rjung
Date: Tue May 8 08:17:01 2007
New Revision: 536218
URL: http://svn.apache.org/viewvc?view=rev&rev=536218
Log:
Adding more dreams and some svn properties to the roadmap :)
Modified:
tomcat/connectors/trunk/jk3/ROADMAP (contents, props changed)
Modified: tomcat/connectors/trunk/jk3/ROADMAP
URL: http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk3/ROADMAP?view=diff&rev=536218&r1=536217&r2=536218
==============================================================================
--- tomcat/connectors/trunk/jk3/ROADMAP (original)
+++ tomcat/connectors/trunk/jk3/ROADMAP Tue May 8 08:17:01 2007
@@ -1,43 +1,52 @@
-APACHE TOMCAT JK3 CONNECTOR ROADMAP -*-text-*-
-
-ApacheCon EU 2007 DISCUSSION POINTS:
-
- * Lets make next generation connector and software load balancer
- for application servers.
- * Lets put JK 1.2 in maintenance mode
- - Stop adding things to the JK 1.2 and only fix bugs
- - We'll still need to vote how to maintain this
- * It should be APR based and supported platforms should be
- - Apache Httpd 2+
- - Microsoft IIS 5+ (Windows 2000 and up)
- - Generic API for standalone based programs
- * Java code will be Java5 based
- - Java5 is mandatory
- - Both server and client reference implementation
- will be developed
- * Scripting support for the Load Balancer
- - Load balancer will have some sort of scripting
- to be able to make rule based load balancers
- - We still have to decide if we need a full-blown
- scripting support, or a simple rule engine will do
- * Extended AJP 1.3 protocol
- - Keep AJP 1.3 backward compatible
- - CPING/CPONG will be mandatory when establishing
- new connections.
- - Add connection close notification.
- Done by extending CPING/CPONG
- - See how we can have 64K+ headers
- Idea is to treat them as POST data if the
- header doesn't fit inside header AJP packet
- * Make JK3 protocol independent
- - Although developed with protocol independence in mind
- JK 1.2 is practically unusable for non AJP 1.3 protocols.
- JK3 should allow custom protocols like http or fastcgi
- * Add persistence to the dynamic configuration
- - Have a way to merge the static configuration with
- modified dynamic configuration via jkstatus
- * Add management thread for each child
- - APR_HAS_THREADS presence will be mandatory
- - For each child process in web server a management thread
- will be created that will monitor state and dynamic
- configuration.
+APACHE TOMCAT JK3 CONNECTOR ROADMAP -*-text-*-
+
+ApacheCon EU 2007 DISCUSSION POINTS:
+
+ * Lets make next generation connector and software load balancer
+ for application servers.
+ * Lets put JK 1.2 in maintenance mode
+ - Stop adding things to the JK 1.2 and only fix bugs
+ - We'll still need to vote how to maintain this
+ * It should be APR based and supported platforms should be
+ - Apache Httpd 2+
+ - Microsoft IIS 5+ (Windows 2000 and up)
+ - Generic API for standalone based programs
+ * Java code will be Java5 based
+ - Java5 is mandatory
+ - Both server and client reference implementation
+ will be developed
+ * Scripting support for the Load Balancer
+ - Load balancer will have some sort of scripting
+ to be able to make rule based load balancers
+ - We still have to decide if we need a full-blown
+ scripting support, or a simple rule engine will do
+ * Extended AJP 1.3 protocol
+ - Keep AJP 1.3 backward compatible
+ - CPING/CPONG will be mandatory when establishing
+ new connections.
+ - Add connection close notification.
+ Done by extending CPING/CPONG
+ - See how we can have 64K+ headers
+ Idea is to treat them as POST data if the
+ header doesn't fit inside header AJP packet
+ * Make JK3 protocol independent
+ - Although developed with protocol independence in mind
+ JK 1.2 is practically unusable for non AJP 1.3 protocols.
+ JK3 should allow custom protocols like http or fastcgi
+ * Add persistence to the dynamic configuration
+ - Have a way to merge the static configuration with
+ modified dynamic configuration via jkstatus
+ * More powerful log framework
+ - Using hierarchical logger names with corresponding
+ log levels to be able to debug or trace only
+ appropriate parts of the code
+ * Add management thread for each child
+ - APR_HAS_THREADS presence will be mandatory
+ - For each child process in web server a management thread
+ will be created that will monitor state and dynamic
+ configuration.
+ * COMET support
+ - Finding our ways how to drop idle connections between web
+ server and backend
+ - Maybe transporting the backend connector events back to the web
+ server
Propchange: tomcat/connectors/trunk/jk3/ROADMAP
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: tomcat/connectors/trunk/jk3/ROADMAP
------------------------------------------------------------------------------
svn:keywords = Author Date Id Revision
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org