Rainer Jung wrote:
Hello,
I'm thinking about branching JK, so adding
http://svn.apache.org/viewvc/tomcat/connectors/branches/jk1.2.x
and initially populate the branch with the contents of the 1.2.28 tag.
The motivation is to stabilize 1.2 and restrict further changes on 1.2
to patches only.
No need for the branching thought.
Just create jk3 and take a blank sheet of paper :)
Option A) The big new thing
We collected ideas for a JK3 some years ago. Those included e.g.
migrating to APR and other big changes.
I like this idea better.
The problem with mod_proxy and mod_cluster is the
fact they are targeted for a *single* web server (httpd)
They don't have the generic web server API like mod_jk
does, and all of them doesn't support async behavior.
There is simply limitation in both AJP13 and Httpd protocol
that prevents something like that if one wish to
have both async, secure and persistent connections
from the web server to the app server.
And we should probably consider to maintain and release
the entire stack both native and java as one entity,
not like now picking bits of connector inside the
core tomcat. IMO tomcat should ship with one or
two own pure java connectors. If someone needs
the web server connector he should pick one from
the connector project together with native part.
Regards
--
^(TM)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
