>On Thu, Jun 14, 2001 at 10:28:47AM +0200, GOMEZ Henri wrote: >> mod_jk support Apache 2.0 >> >> And TC 4.0 as preliminary support for ajp13 used >> in mod_jk. >> >> Could you take a look at it ? > >Okay, what's the difference between mod_webapp and mod_jk? I thought >that mod_webapp was the preferred TC 4.0 connector? This seems like >this is worthy of a FAQ. We've still got people using mod_jserv... One of the goal of j-t-c, is to be the answer to : 'how to connect my webserver to tomcat ?' A great effort has been deployed in having an easy to use build stuff. Next effort will be documentation and ........... lobbying :) >Oh, is it that mod_webapp uses the Warp protocol, not ajp13? Does >ajp13 support the TC 4.0 hot-deploy functionality? -- justin not in ajp13. But it's successor ajp14, have a strongest login procedure, and autoconf support (uri handled passed to web-server). Also planned is to inform the web-server of context state, ie when a context is put down (for admin purpose), the web-servlet must learn it and route request to another servlet-engine (if we are in load-balancing configuration). what make me think we should add a fault-tolerant/backup-mode worker in mod_jk. A la load-balancing, having a group of worker (servlet engine), with one principal, and many as backup. If the principal could no more handle a request (failure or context down), just have the request routed to next worker in list. What about ?
