Fine to see mod_webapp back to life :)
1) You added many features interesting in building (autoconf, apr)
which we could study to adapt to mod_jk (at least autoconf).
2) I plan to update the mod_webapp RPM and hope the code will compile
under GCC (it wasn't the case with tc 4.0b2/b3)
3) You still didn't tell us what you think into merging mod_webapp
and mod_jk.
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.
Much more what about using the connector to have the Apache
store sessions (serialized) data from Tomcat.
Here is the idea :
- One Apache may be connected to multiple Tomcat (TomcatA/TomcatB).
- Each Tomcat have sessions related data which may be good to
see available to other Tomcats in case of failure :
ie:
TomcatA create a session and data in that session.
When replying to Apache (via mod_jk or mod_webapp) it also
send the session datas (serialized) when they are created
(or updated).
Apache store that informations for possible future use (db1/gdb)
TomcatA fail (stopped, restarted, jvm dumped...) and Apache
(via at least mod_jk) decide to route the request to TomcatB.
TomcatB miss the session datas allready generated by TomcatA but
Apache could route the request ALONG WITH THE previously saved
session
informations. TomcatB could then recreate the session, set the
session data and then serve the request in the same condition that
TomcatA.
You get a real fault-tolerant system (no need to resign in some
case).
What do you think about that proposal (Costin, Craig, Dan, Jon, Pier...)
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
