On Thu, 28 Mar 2002 [EMAIL PROTECTED] wrote: > Maybe I've not kept up on the docs enough but ... > > I do think this thread, highlights a general confusion around tomcat. > Over the last couple of years, there have been many > mod_jk/jk2/webapp/warp/?? implementations, ajp versions etc, and even > when the discussions are on the list, it's still hard to be able to say > (for lowly thread lurkers/tomcat users like myself), tomcat X.x can use > mod_??, on ajp?.? because they provide xyz..
The problem is I have no time and I'm not good at writing docs. Mod_jk works on all web servers and with all tomcat versions. Mod_jk2 will do the same. The core of the confusion is the distinction between "protocol", "API", "implementation". A protocol is something like IIOP, RPC, HTTP. The API is a set of functions - for forwarding the request, getting response, config, auth, etc. Mod_jk is an implementation that supports multiple communication protocols and multiple APIs. Different versions of tomcat also support multiple protocols and APIs. There are 4 protocols we use: - ajp12 ( in tomcat3.x, jserv ) - ajp13 ( in tomcat3.x, tomcat4.x ) - jni ( in tomcat3.x - and 4.x as soon as jk2 is ready ) - WARP ( in tomcat4.x ) There are several APIs: - request forwarding APIs - usually one method signature for each protocol - configuration methods - in warp and what used to be called ajp14 ( very confusing, since it was a set of new methods implemented with ajp13 protocol ) - auth, shutdown, etc - again 2 or 3 if you count the 4.0 shutdown protocol. And several implementations of those protocols: - mod_jserv implements ajp12 - mod_jk implements ajp12, ajp13, jni - mod_jk2 implements ajp13 ( and one of my goals for a future version is to implement one 'real' protocol - a minimal subset of RPC/XDR or IIOP or similar ) ( with jni replaced with ajp13 - and multiple channels - tcp, unix, jni ) - mod_webapp implements WARP - tomcat3.x implements ajp12, ajp13, jni - tomcat4.x - ajp13, WARP And several implementations of the APIs ( similar matrix ). The basic request forwarding APIs used in jk is common to all servers and should be fully interoperable. Extended APIs ( config, etc) are supported only in new versions of tomcat/jk. Load balancing is one extra feature in mod_jk and mod_jserv, on top of the forwarding API. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
