> Why not use mod_webapp/mod_jk to start the
> web-connector sub-project allowing us to remove many question
> related to connectors from Tomcat user/dev lists ?
>
> The same web-connector project could be used against
> Tomcat 3.2/3.3/4.0 but not be restricted to Tomcat.
> Any project understanding the concept of HTTP request/reply
> could use it.
Creating a new project with the connector is probably a too big overhead.
Much better would be to start a revolution ( in proposals), use the
current code as a starting point and merge ( or modularize ) features.
When it's ready - it can be proposed as a replacement to both mod_jk and
mod_webapp.
I would go one step ahead - and do this for both C side and java
side. There are quite a few optimizations you can do by keeping those in
sync, and it's very likely the result will be faster and better than any
of the current connectors ( at least mod_jk was never optimized
seriously, most work was put into the core and infrastructure ).
In 3.3 the connector is just a regular interceptor - when the revolution
is ready it'll be just a matter of config change.
> Much more what about using the connector to have the Apache
> store sessions (serialized) data from Tomcat.
I'm not sure it's the most important problem to solve - easier
configuration is probably more usefull for more people.
But if you need such thing - mod_jk is modular enough.
Costin
