Dan, It seems the most requested ( and important) feature for mod_jk is simpler configuration - and I think we can do many simple things with a lot of effect ( sending the config automatically is one - and quite easy ). Regarding the use of mod_jk for tomcat4 - I would sugest a different aproach: The connector is a mini ORB, optimized for HTTP-type requests. On the Java side, tomcat3.3 does a lot of optimizations - most of them related with object allocation and representation. I think those pieces are very valuable - and instead of implementing the AJP13 ( and future 14 ) it would be much better to extract the full implementation and make it independent of tomcat3.3 That would allow to also build a tomcat3.2 adapter ( since most people are using 3.2 right now - and changing a production site is a slow process ). Tomcat4 is supposed to be more flexible than 3.x :-) - so creating an adapter should be easy ( well, I don't understand most of the 4.0 design, but I was able to build a prototype adapter - and get ajp13 support into 4.0. Unfortunately my head exploded due to class loading problems - but it can be done ). So what I would do ( or I'll do :-) is start with a new package, taking MessageBytes, MimeHeaders, subset of Request/Response, add an adapter interface ( tc3.1 used to have one - but it had a bad design - I can say that since I did it ) using a notification model ( for example a AdapterListener that will allow the adapter to plug to upper layers ) Then create interceptors/valves for 3.2, 3.3, 4.0 ( maybe:-) and plug it in. Of course, this is just an idea - there are many details to discuss ( and other, better ideas - I'm sure of that :-). Costin On Tue, 24 Apr 2001, Dan Milstein wrote: > One thing which I think would be useful (which I wanted to do myself, but > don't think I'll have time to do), would be to write an ajp13 connector for > TC 4. This would allow TC 4 users to use mod_jk as their plugin (which > supports iPlanet and IIS). If you are interested in doing some development, > I think that would be an excellent contribution. > > Steps: > > - Take a look through the Ajp13 doc in the 3.3 branch (src/doc/AJPv13.html) > -- this explains how the protocol works. > > - Review the ajp13 connector code in 3.3 > (share/org/apache/tomcat/modules/server/Ajp13.java and > Ajp13Interceptor.java). > > - Adapt that code to the TC 4 codebase (basing on HttpConnector, or > WarpConnector, possibly). > > Wins: connect to multiple servers (including netscape and iis), load > balancing, debugged C code. > > Losses: painful to configure > > Although I don't have time to write this code myself, I can contribute some > help (I understand the 3.3 ajp13 code pretty thoroughly). > > -Dan > > > Kevin Seguin wrote: > > > > i want to move from tomcat 3.x to tomcat 4. i absolutely must be able to > > use tomcat 4 with netscape/iplanet and microsoft (iis) web servers. as > > near as i can tell, the only connector that will be available in the > > foreseeable future is for apache 1.3. is this true? > > > > i have come across very little (almost no) information regarding this new > > webapp lib (which appears to be undergoing some significant change > > recently) and the warp thing... does *anybody* have anything to share?? > > i'm willing to help out with connector development, or even write my own > > connectors... if i could only figure out where to start... > >
