You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by mt...@apache.org on 2007/05/08 17:05:25 UTC
svn commit: r536215 - in /tomcat/connectors/trunk/jk3: ./ ROADMAP
Author: mturk
Date: Tue May 8 08:05:24 2007
New Revision: 536215
URL: http://svn.apache.org/viewvc?view=rev&rev=536215
Log:
Lets move things :)
Added:
tomcat/connectors/trunk/jk3/
tomcat/connectors/trunk/jk3/ROADMAP
Added: tomcat/connectors/trunk/jk3/ROADMAP
URL: http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk3/ROADMAP?view=auto&rev=536215
==============================================================================
--- tomcat/connectors/trunk/jk3/ROADMAP (added)
+++ tomcat/connectors/trunk/jk3/ROADMAP Tue May 8 08:05:24 2007
@@ -0,0 +1,43 @@
+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.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r536215 - in /tomcat/connectors/trunk/jk3: ./ ROADMAP
Posted by Henri Gomez <he...@gmail.com>.
Great !
2007/5/8, Jim Jagielski <ji...@jagunet.com>:
> Cool!
>
> On May 8, 2007, at 11:05 AM, mturk@apache.org wrote:
> > URL: http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk3/
> > ROADMAP?view=auto&rev=536215
> > ======================================================================
> > ========
> > --- tomcat/connectors/trunk/jk3/ROADMAP (added)
> > +++ tomcat/connectors/trunk/jk3/ROADMAP Tue May 8 08:05:24 2007
> > @@ -0,0 +1,43 @@
> > +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.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: svn commit: r536215 - in /tomcat/connectors/trunk/jk3: ./ ROADMAP
Posted by Jim Jagielski <ji...@jaguNET.com>.
Cool!
On May 8, 2007, at 11:05 AM, mturk@apache.org wrote:
> URL: http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk3/
> ROADMAP?view=auto&rev=536215
> ======================================================================
> ========
> --- tomcat/connectors/trunk/jk3/ROADMAP (added)
> +++ tomcat/connectors/trunk/jk3/ROADMAP Tue May 8 08:05:24 2007
> @@ -0,0 +1,43 @@
> +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.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org