tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher K. St. John" <...@distributopia.com>
Subject Re: jakarta-tomcat-connectors documentation/summaries
Date Sun, 28 Apr 2002 21:04:38 GMT

 The following document is very incomplete, and in many
cases factually incorrect. The idea is to post it now, while
it's obviously in draft form, get feedback, and then clean it
up and publish it wherever would be most useful (jakarta-tomcat
connectors page, or the Tomcat FAQ)

 I'm currently tracking down user-level instructions for all the
connector/webserver/container combinations I can find, so pointers
to those are especially welcome. I'm not wedded to any of the listing
categories, or the format, or pretty much anything else, so if you
don't like it, speak up.


----------------------------------------------------------------


mod_jserv

 why it was written:
   it was there first. 

 where to get the source:
   java-jserv repository

 where to get documentation:
   java-jserv repository

 unerlying protocol:
   AJP11   

 works with:
   servlet containers:
     JServ
   web servers:
     old versions of Apache httpd
   operating systems:
     ???

 underlying protocol:
   AJP11


mod_jk

   should jk2 be listed out separately?

   why it was written:
     originally, clean-up of mod_jserv. 

   status:
     in production for tomcat 3, 4

   where to get the source:
     jakarta-tomcat-connectors/jk

   where to get documentation:
     jakarta-tomcat-connectors/jk
     tomcat-dev mailing list archives
     http://jakarta.apache.org/tomcat/tomcat-3.3-doc/mod_jk-howto.html
     http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk.html
     http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk2.html

   primary developers:
     evolved from mod_jserv (see above)
     Gal Shachor, IBM Research, Haifa Lab. refactored mod_jserv
     many others?

   works with:
     servlet containers:
       jserv?
       tomcat-3
       tomcat-4
     web servers:
       domino
       apache 1.3
       apache 2.0?
       netscape
       others?
     platforms:
       lots?

   it's big thing:
     production use

   underlying protocol:
     AJP, see mod_jserv
     evolution:
       AJP12, binary
       AJP13, better SSL support. the current protocol.
       AJP14, in testing. see "comments" below.

   special powers:
     load balancing with both tomcat 3 and tomcat 4

   documentation/mailing-list/cvs comments of interest:

   "Mod_jk v/s mod_webapp" on tomcat-dev: 

     Bill Barker wrote: "mod_jk2 is the next generation of mod_jk.  It
     is currently barely Alpha quality for Apache 2.x (and still
     subject to major changes from day-to-day)"

     <costinm@covalent.net>: "It works ( barely :-) with Apache2.x and
     1.3. The connector for apache1.3 can be used as a basis for
     updating IIS/iPlanet."

     costin: "Mod_jk works on all web servers and with all tomcat
     versions. Mod_jk2 will do the same."
 
     <costinm@covalent.net> : "What we called "ajp14" are a set of new
     APIs for config, shutdown, MD5 auth - added by Henri. Ajp14 API
     is not 'released', and the current plan is to postpone it after
     the first release of jk2"
     
     <costinm@covalent.net> : "it started with ajp11 and ajp12 ( first
     text based, second binary ).  Ajp12 evolved into ajp13 - using
     same encoding but with some extensions ( to deal with persistent
     connections ).

     "GOMEZ Henri" <hgomez@slib.fr> : using jk instead of warp depend
     on webserver you want to have it.  If need today, or tomorrow
     IIS/NES/DOMINO, use mod_jk, if you only need to use Apache
     1.3/2.0 and have APR ready, you can use also mod_warp.

     costin: "jk had many developers contributing to it, more than any
     other tomcat component ( AFAIK ). It's also a matter of evolution
     - mod_jk started by implementing the ajp12 protocol and beeing
     backward compatible with mod_jserv ( actually a lot of code has
     been refactored from it ). You can still use mod_jserv with 3.x,
     and you can use mod_jk with anything from jserv to tomcat4."


 webapp

   you might see the terms "mod_webapp", "webapp" and "WARP", being
   used in a confusingly similiar way, but properly: mod_webapp - the
   apache module portion of webapp, WARP - the underlying protocol

   why it was written:
    uses APR, tight tomcat 4 intergration

   status:
     ???

   where to get the source:
     jakarta-tomcat-connectors/webapp

   where to find documentation:
     jakarta-tomcat-connectors/webapp
     http://nagoya.apache.org/~pier/
     http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/webapp.html

   works with:
     tomcat versions:
       tomcat-4
       others?
     web servers:
       apache 1.3
       others?
     operating systems:
       "not windows"?

   underlying protocol:
     WARP

   special powers:
     tight webserver/container integration means simple deployments
     are very easy

   primary developers:
     Pier Fumagalli <pier@betaversion.org>
     others?

   mailing list/documentation comments:

   Pier Fumagalli <pier@betaversion.org> : "I just said that for what
   matters to me (meaning, for what I use it, it works
   allright)... That's far from saying that I'm no longer interested
   on it."

   mod_jk vs mod_webapp thread: pier : "Motivation? I don't like
   mod_jk, I wanted to use APR as a portable runtime for an Apache 1.3
   module, I believe that the WARP protocol with built-in support for
   auto-deployment and web-application configuration is the way to go
   (rather than using mod_rewrite rules all the way around),"


 coyote

   coyote isn't properly a webserver connector like the others listed
   above, see cvs comments below.

   why it was written:
     ???

   status:
     being phased in as default for tomcat 4.1

   where to get the source:
     jakarta-tomcat-connectors/coyote
     org/apache/coyote/http11 - standalone http 1.1 connector

   where to get documentation:
     no documentation as such? mailing list archives, cvs notes only?

   works with:
     servlet containers:
      tomcat-3
      tomcat-4
     web servers:
      using jk2: apache 1.3
      apache 2.0 status?
      others?
     operating systems:
       ??

   underlying protocol:

     HTTP, as standalone connector for tomcat 4 (3?)

     AJPXX ref:  Re: [VOTE] Release Plan for Apache Tomcat 4.1 
     Wed, 24 Apr 2002 13:29:22 -0700 (PDT) <costinm@covalent.net>
     coyote-Jk2 is stable as a Ajp13/Socket connector - i.e. all that
     matter for mod_jk1. The Unix socket and all advanced features of
     jk2/java will not be 'release quality' either ( but with a bit of
     luck and some help from Nacho and maybe others we can have them
     working and beta-level).

   primary developers:
     "Remy Maucherat" <remm@apache.org>
     others?

   mailing list/documentation/cvs comments:

   coyote announcement? from cvs: Thu Jun 14 01:07:52 2001 UTC (10
   months, 1 week ago) by remm "Coyote is a proposal for a "new"
   connector API for Tomcat. It actually isn't that new, because it is
   derived from some of the components which are at the core of Tomcat
   3.3. Those components were significantly simplified."

   From: "Remy Maucherat" <remm@apache.org>
   Subject: Re: Coyote/jk2 - interaction explanations please
   Date: Thu, 18 Apr 2002 04:45:37 -0700
   In Coyote, there's:
   - the container adapters (for 3.3, 4.0, 4.0-HEAD)
   - the external API (request, response, and a couple other things)
   JK 2 and HTTP/1.1 are protocol handlers for Coyote.


 
-- 
Christopher St. John cks@distributopia.com
DistribuTopia http://www.distributopia.com

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message