RE: jakarta-tomcat-connectors documentation/summaries
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: jueves 2 de mayo de 2002 5:16 For me is controversial to have a document at jakarta, that affirms that prior to webapp, mod_jk was unmaintained, mainly because we have maintained itall the time. Costin, Henri, Dan , Larry , Me, and much others done the work, so apart from not be true, i think is offensive to all that done that work, and contributed his time to support it.. So get rid the of the citation, or do not include that affirmation, thanks.. ( and of course all others are very valid reasons to try other way, more, to try another way is ever good :) Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
Ignacio J. Ortega wrote: De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: jueves 2 de mayo de 2002 5:16 For me is controversial to have a document at jakarta, that affirms Speaking of having a document at jakarta, it isn't there yet. And it won't go live unless everyone likes it (think We are the world as sung by a chorus of tomcat developers, all holding hands, etc). So no worries. I think it may have reached the better than nothing stage, and I'd like to start formatting and cleanup. That presupposes a destination. I originally talked to Henri Gomez about hanging it off a jakarta-tomcat-connectors page, but Glenn Nielsen also mentioned a Tomcat FAQ. Where should it go? -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: jueves 2 de mayo de 2002 15:44 Speaking of having a document at jakarta, it isn't there yet. And it won't go live unless everyone likes it (think We are the world as sung by a chorus of tomcat developers, all holding hands, etc). So no worries. This is a public list, so unless this thread is not archived anywhere :), which i doubt, this has reached the status of a jakarta document with his mere existence, hang or not the doc in the site, is an implementation detail :). I think it may have reached the better than nothing stage, and I'd like to start formatting and cleanup. That presupposes a destination. I originally talked to Henri Gomez about hanging it off a jakarta-tomcat-connectors page, but Glenn Nielsen also mentioned a Tomcat FAQ. Where should it go? Good question, but the usual rules apply, do it and if anybody finds a better place, he can move it later :), you are a committer!!, remember?? :).. so your actions can go before your words :)).. If i can talk about lessons learned here, actions are much less discussed than mail list messages :)), and that any newbie committer breaks the build in his first commit :), may be you will break our traditions :), i dont know which will be worse.. ;) Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
An URL to add : http://www.ubeans.com/tomcat/index.html - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Christopher K. St. John [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 7:54 PM To: [EMAIL PROTECTED] Subject: RE: jakarta-tomcat-connectors documentation/summaries Another update. Same disclaimers as before. FAQ's (just an idea, these don't have to be included) Q: Is mod_webapp replacing mod_jk? A: No. See below for links to documentation, then choose the one that best suits your needs. Q: Is Coyote replacing mod_jk? A: Coyote isn't the same sort of thing as mod_jk, see below in the Coyote section for more details. Q: It's all very confusing. A: Yes. A good strategy is to read through the summaries below and follow some of the documentation links. If you still have questions, try searching the tomcat-user mailing list archives, someone has probably answered the question already, there may even be a HOWTO already prepared. If that doesn't help, then you might consider posting your question to tomcat-users. non-jakarta howto's: these were culled from recent posts to tomcat-users. i have no way to judge if they are any good. it would be nice to only include the ones that someone can vouch for, but that may be too much work. the list is evolving... http://www.acg-gmbh.de/mod_jk/ Apache 2.0/Tomcat 4/mod_jk/Win32 http://www.pubbitch.org/jboss/ Apache 2.0/Tomcat 4/mod_jk2/JBoss Apache 2.0/Tomcat 4/mod_webapp/JBoss http://bruno.vernay.free.fr/HowTo/bWebServerHowTo/index.html Apache ?.?/Tomcat 4/mod_webapp/Win32 references link has list of other HOWTO's mod_jserv although it's probably still in production use at some sites, mod_jserv generally shouldn't be considered for new installations. why it was written: it was there first. where to get the source: jakarta-tomcat repository src/native/mod_jserv/ where to get documentation: http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-apache-h owto.html [ed] In tomcat-3.3-doc/index.html, it looks like mod_jserv is the suggested connector, and mod_jk is optional or alternative or something. It's my understanding that this is incorrect, and mod_jk should be used for new installations. It's a little confusing. unerlying protocol: AJP11 - original protocol Ajp12 - also supported in mod_jk1. works with: servlet containers: JServ Tomcat3.x as well ( which supports ajp12 ) web servers: All apache1.3 versions operating systems: ??? mod_jk why it was written: originally, clean-up of mod_jserv. Refactoring of mod_jserv to better abstract the server and protocol. features: many production users. load balancing with both tomcat 3 and tomcat 4 [EMAIL PROTECTED] Pretty good OO model, good abstraction for server and protocol, etc. future: mod_jk2, as of [30 Apr 2002] still in pre-alpha. status: in production for tomcat 3, 4. see also webapp connector. 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 works with: servlet containers: jserv? tomcat-3 tomcat-4 web servers: domino apache 1.3 apache 2.0 (HEAD) netscape AOLServer ( not in the main tree ). IIS platforms: many. underlying protocol: AJP, see mod_jserv evolution: AJP12, binary AJP13, better SSL support. the current protocol. AJP14, there is no AJP14, it's a shelved experiment. AJP13 is flexible enough for future growth, and there's the possibility of eventually moving to an industry-standard marshalling protocol like XDR or CDR. see comments below. documentation/mailing-list/cvs comments of interest: Re: [NITPICK] didn't see this one coming... Mon, 29 Apr 2002 07:54:09 -0700 (PDT) [EMAIL PROTECTED] ... Note that mod_jk2 is not and will not be ready for 4.1 ... [EMAIL PROTECTED] Also - it's [mod_jk -ed] the area/component of tomcat with the largest number of individual commiters ( by my count at least ). And more important - one of the things that 3.x and 4.x share and seem to bring cooperation from both sides. 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
Re: jakarta-tomcat-connectors documentation/summaries
On Thu, 2002-05-02 at 23:43, Christopher K. St. John wrote: think We are the world as sung by a chorus of tomcat developers, all holding hands, etc). He, he, I like this one :-) Bojan -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
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 being 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 features: tight webserver/container integration means simple deployments are very easy, work being done on making things even easier. why it was written: uses APR, tight tomcat 4 intergration status: under active development. 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 only web servers: apache 1.3 apache 2.0 [EMAIL PROTECTED] with the prefork MPM. We have some experimental code in the repository to add ... Apache 2.0 with the other MPMs. operating systems: OS/X (confirmed by pier) Solaris 8 both X86 and SPARC (confirmed by pier) should work on all other Unix-like O/S's experimental code in repository to support Apache 1.3 under Windows underlying protocol: WARP mailing list/documentation comments: 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), Re: jakarta-tomcat-connectors documentation/summaries pier: There were some other motivations when it all started... Mod_JK was unmaintained, and nobody knew how to make it work. I didn't like its design and took out the experiences I had while working on mod_jserv and all those nifty ideas, and put them together (note: the WARP protocol is a derivate of AJPv21 which was supposed to be used on JServ.NEXT) coyote coyote isn't properly a webserver connector like the others listed here. see cvs comments below. it's: coyote - the architecture for the java code that talks to connectors. similiar to code in tomcat 3.3, but adapters are available for both tomcat 3 and tomcat 4. coyote http - an implementation of an HTTP standalone connector. coyote jk - interface to mod_jk (see above) why it was written: costin: Lots of optimizations ( especially in 4.0 ), better abstractions, etc. status: being phased in as default for tomcat 4.1 costin: Will also be the main connector for 3.x ( at least for jk2, but also http/1.1 ) where to get the source: jakarta-tomcat-connectors/coyote org/apache/coyote/http11 - standalone http 1.1 connector where to get documentation: user docs: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk2.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html developer docs: cvs comments, mailing list works with: servlet containers: tomcat-3 tomcat-4 web servers: see mod_jk operating systems pure Java for HTTP standalone same as mod_jk for jk configuration underlying protocol: HTTP, as standalone connector for tomcat 3/4 AJP13, when used with mod_jk. JNI, (ref remm comment below) mailing list/documentation/cvs comments: Re: [VOTE] Release Plan for Apache Tomcat 4.1 Wed, 24 Apr 2002 13:29:22 -0700 (PDT) [EMAIL PROTECTED] 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). costin: Coyote is the architecture for the java side - it supports HTTP/1.1 ( as standalone ) and all servers that jk1 supports. 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
RE: jakarta-tomcat-connectors documentation/summaries
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 being 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 features: tight webserver/container integration means simple deployments are very easy, work being done on making things even easier. why it was written: uses APR, tight tomcat 4 intergration status: under active development. 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 only web servers: apache 1.3 apache 2.0 [EMAIL PROTECTED] with the prefork MPM. We have some experimental code in the repository to add ... Apache 2.0 with the other MPMs. operating systems: OS/X (confirmed by pier) Solaris 8 both X86 and SPARC (confirmed by pier) should work on all other Unix-like O/S's experimental code in repository to support Apache 1.3 under Windows underlying protocol: WARP mailing list/documentation comments: 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), Re: jakarta-tomcat-connectors documentation/summaries pier: There were some other motivations when it all started... Mod_JK was unmaintained, and nobody knew how to make it work. I didn't like its design and took out the experiences I had while working on mod_jserv and all those nifty ideas, and put them together (note: the WARP protocol is a derivate of AJPv21 which was supposed to be used on JServ.NEXT) coyote coyote isn't properly a webserver connector like the others listed here. see cvs comments below. it's: coyote - the architecture for the java code that talks to connectors. similiar to code in tomcat 3.3, but adapters are available for both tomcat 3 and tomcat 4. coyote http - an implementation of an HTTP standalone connector. coyote jk - interface to mod_jk (see above) why it was written: costin: Lots of optimizations ( especially in 4.0 ), better abstractions, etc. status: being phased in as default for tomcat 4.1 costin: Will also be the main connector for 3.x ( at least for jk2, but also http/1.1 ) where to get the source: jakarta-tomcat-connectors/coyote org/apache/coyote/http11 - standalone http 1.1 connector where to get documentation: user docs: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/jk2.html http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/coyote.html developer docs: cvs comments, mailing list works with: servlet containers: tomcat-3 tomcat-4 web servers: see mod_jk operating systems pure Java for HTTP standalone same as mod_jk for jk configuration underlying protocol: HTTP, as standalone connector for tomcat 3/4 AJP13, when used with mod_jk. JNI, (ref remm comment below) mailing list/documentation/cvs comments: Re: [VOTE] Release Plan for Apache Tomcat 4.1 Wed, 24 Apr 2002 13:29:22 -0700 (PDT) [EMAIL PROTECTED] 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). costin: Coyote is the architecture for the java side - it supports HTTP/1.1 ( as standalone ) and all servers that jk1 supports. 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
Re: jakarta-tomcat-connectors documentation/summaries
Christopher K. St. John wrote: Another update. Same disclaimers as before. Mail client mishap, second one's a duplicate, sorry. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: miércoles 1 de mayo de 2002 19:44 webapp Re: jakarta-tomcat-connectors documentation/summaries pier: There were some other motivations when it all started... Mod_JK was unmaintained, and nobody knew how to make it work. I didn't like I disagree with Pier here. ( sorry i've lost the original Pier's menssage ) I can admit all other reasons, but jk never has been unmaintained for any period of time in the past, more, prior to webapp announce, or more or less at the same time, Dan Milstein and Henri did a big work documenting and studiying the sources, the protocol and the api.. and never a bug in jk was left in the bag, perhaps due to it's nature was and is very difficult to track every bug in every platform and http server it supports, i admit.. but never run out of support.. Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
On Thu, 2 May 2002, Ignacio J. Ortega wrote: I can admit all other reasons, but jk never has been unmaintained for any period of time in the past, more, prior to webapp announce, or more or less at the same time, Dan Milstein and Henri did a big work documenting and studiying the sources, the protocol and the api.. and I think I've also been around since jk was written until now. ( I even wrote a lot of the java code, and some pieces of C ) True, I'm not very fast on fixing bugs or documentation - and sometimes I have the same attitude 'works for me' as Pier. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
Ignacio J. Ortega wrote: Re: jakarta-tomcat-connectors documentation/summaries pier: There were some other motivations when it all started... Hmmm. The theory is that the document should be absolutely 100% non-controversial. Other parts of the entry already emphasize ease of use, so I don't think removing the quote would change the meaning. Is that acceptable to everyone, including Pier? If not, let me know, otherwise the quote goes. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
The only limitation is that it support only 255 methods ( unless we use an expansion ), since it has a byte as method code ( to facilitate table-based dispatching ). 255 methods should be suffisant since we could have the generic get/set property method ;) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
Ok, I'm maybe being thick here, but I want to make sure I've got this straight. The idea is that anyone who's clueful enough to search the archives is likely to come across the term AJP14, so it's best to give them a hint (even if term isn't going to mean anything to somebody who just wants to evaluate the current set of connectors) So, to confirm: AJP13 defines marshalling protocols. It also has a command set that uses those marshalling protocols. AJP14 uses the same marshalling protocol as AJP13, but extends the command set. The distinction is important, because in the past major version number changes in AJP meant an entirely new binary protocol. AJP14 is for the future, sometime after the release of jk2. It's still being discussed. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
mod_jk and mod_jk2 do not work properly with Apache 2.0. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
Which version of Apache 2.0 ? Which version of mod_jk (from jtc ?) Did you try mod_jk from tomcat-3.3.1 ? - Henri Gomez ___[_] EMAIL : [EMAIL PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 -Original Message- From: Pascal Forget [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 5:24 PM To: Tomcat Developers List Subject: Re: jakarta-tomcat-connectors documentation/summaries mod_jk and mod_jk2 do not work properly with Apache 2.0. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
On Mon, 29 Apr 2002, Christopher K. St. John wrote: Ok, I'm maybe being thick here, but I want to make sure I've got this straight. The idea is that anyone who's clueful enough to search the archives is likely to come across the term AJP14, so it's best to give them a hint (even if term isn't going to mean anything to somebody who just wants to evaluate the current set of connectors) So, to confirm: AJP13 defines marshalling protocols. It also has a command set that uses those marshalling protocols. AJP14 uses the same marshalling protocol as AJP13, but extends the command set. The distinction is important, because in the past major version number changes in AJP meant an entirely new binary protocol. AJP14 is for the future, sometime after the release of jk2. It's still being discussed. No. AJP14 was an experiment to extend AJP13 - but we agreed that keeping Ajp13 stable and frozen and stable ( and remaining compatible with the whole range of tomcats ) is better than whatever improvements we could gain. And I strongly believe that in the future we'll either stick with ajp13, or implement a subset of XDR or CDR - i.e. a standard marshalling ( and an even smaller subset of the rpc semantics ). To avoid confusion, we should stop discussing about Ajp14 - and stop using the same term for protocol and API. There is one wire ( binary ) protocol, ajp13. PROPOSAL: let's use 'jk1 API' to refer to the set of methods/callbacks used in jk1 - that's the base API that is supported in all tomcat versions ( starting with 3.2 ). The only reference to ajp14 should point that there is no ajp14. Ajp13 was designed from start as a RPC-like protocol ( with minimal overhead, etc ), and we don't have any use case where ajp13 wouldn't work. The only limitation is that it support only 255 methods ( unless we use an expansion ), since it has a byte as method code ( to facilitate table-based dispatching ). Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
On Mon, 29 Apr 2002, Pascal Forget wrote: mod_jk and mod_jk2 do not work properly with Apache 2.0. mod_jk works fine with Apache2.0 - at least the CVS HEAD. If someone has the time, we should replace/update the .tar.gz we distribute, that version has a bug that was fixed. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
On Mon, 29 Apr 2002, Pascal Forget wrote: mod_jk and mod_jk2 do not work properly with Apache 2.0. And mod_jk2 is not yet supposed to work ( since it's not even alpha ). But it does :-) Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
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) [EMAIL PROTECTED]: 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. [EMAIL PROTECTED] : 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 [EMAIL PROTECTED] : 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 [EMAIL PROTECTED] : 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 [EMAIL PROTECTED] others? mailing list/documentation comments: Pier Fumagalli [EMAIL PROTECTED] : I just said that for what matters to me (meaning, for what I use it, it works allright)... That's far
Re: jakarta-tomcat-connectors documentation/summaries
On Sun, 28 Apr 2002, Christopher K. St. John wrote: mod_jserv where to get the source: java-jserv repository I would recommend jakarta-tomcat, the version there has been tested the most with tomcat ( there are no significant changes AFAIK ). unerlying protocol: AJP11 Ajp12 - also supported in mod_jk1. works with: servlet containers: JServ Tomcat3.x as well ( which supports ajp12 ). web servers: old versions of Apache httpd All apache1.3 versions. mod_jk should jk2 be listed out separately? Probably not. why it was written: originally, clean-up of mod_jserv. Refactoring of mod_jserv to better abstract the server and protocol. 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 There are some interesting how-tos on the web ( including for lb and tomcat4 ) - maybe we can do a google search and link. primary developers: evolved from mod_jserv (see above) Gal Shachor, IBM Research, Haifa Lab. refactored mod_jserv many others? Check the sources, there are plenty of names there :-) works with: servlet containers: jserv? Well, yes. tomcat-3 tomcat-4 web servers: domino apache 1.3 apache 2.0? netscape others? AOLServer ( not in the main tree ). it's big thing: production use Also - it's the area/component of tomcat with the largest number of individual commiters ( by my count at least ). And more important - one of the things that 3.x and 4.x share and seem to bring cooperation from both sides. underlying protocol: AJP, see mod_jserv evolution: AJP12, binary AJP13, better SSL support. the current protocol. AJP14, in testing. see comments below. No ajp14 protocol - we agreed to stick with ajp13 as a wire protocol ( i.e. no extensions ). Additional APIs will be added but the marshalling will stay the same. My hope is that the next thing will be a standard protocol. special powers: load balancing with both tomcat 3 and tomcat 4 Prety good OO model, good abstraction for server and protocol, etc. [EMAIL PROTECTED]: It works ( barely :-) with Apache2.x and 1.3. The connector for apache1.3 can be used as a basis for updating IIS/iPlanet. That's for mod_jk2 - and I think Nacho got the IIS done ( or close ). [EMAIL PROTECTED] : 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 And we should probably find a better name for it to avoid future confusion between protocol and API. webapp web servers: apache 1.3 others? Apache2. I think they got IIS and iPlanet - don't know what level of support. coyote why it was written: ??? Lots of optimizations ( especially in 4.0 ), better abstractions, etc. status: being phased in as default for tomcat 4.1 Will also be the main connector for 3.x ( at least for jk2, but also http/1.1 ) works with: servlet containers: tomcat-3 tomcat-4 web servers: using jk2: apache 1.3 apache 2.0 status? others? Coyote is the architecture for the java side - it supports HTTP/1.1 ( as standalone ) and all servers that jk1 supports. Coyote-jk is using ajp13 - so works with all jk versions. operating systems: ?? java. primary developers: Remy Maucherat [EMAIL PROTECTED] others? Bill Barker. Costin -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: jakarta-tomcat-connectors documentation/summaries
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Enviado el: lunes 29 de abril de 2002 0:04 mod_jk web servers: domino apache 1.3 apache 2.0? netscape others? AOLServer ( not in the main tree ). IIS webapp web servers: apache 1.3 others? Apache2. I think they got IIS and iPlanet - don't know what level of support. When webapp got support for IIS? I think webapp has got a win32 build for apache, not IIS support AFAIK, Pier could you teach we a little about webapp? ( i'm certaninly hallucinated of see this written on a message to tomcat-dev ;))) ) Saludos , Ignacio J. Ortega -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
Christopher K. St. John [EMAIL PROTECTED] wrote: 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) That's good :) 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. Documentation for webapp is practically non-existant ATM... We need someone volunteering... mod_jserv This can't be decoupled from Apache JServ, it's still an old pre-Foundation project. If Jon agrees (since he seems to be the only one but me who worked on that codebase from the beginning) I would put it in retirement and not even mention it... 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 Correct. why it was written: uses APR, tight tomcat 4 intergration Going to be even tighter for performance... I'm thinking about removing legacy from the Host catalina container, but still not quite figured out a full action plan... status: ??? Works perfectly on all Unix operating systems with Apache 1.3 and Apache 2.0 with the prefork MPM. We have some experimental code in the repository to add multi-threaded support, namedly Apache 1.3 under Windows and Apache 2.0 with the other MPMs. where to get the source: jakarta-tomcat-connectors/webapp Correct. 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 Correct (for now) works with: tomcat versions: tomcat-4 others? Nope... Only Tomcat 4.x and there are no whatsoever plans to integrate it with something else... web servers: apache 1.3 others? Apache 1.3 (non windows) Apache 2.0 (prefork mpm) operating systems: not windows? Not windows ATM, but as I said, the new code is in the repo... underlying protocol: WARP Correct... special powers: tight webserver/container integration means simple deployments are very easy Correct... There might be some evolution on this in the upcoming months (before July). primary developers: Pier Fumagalli [EMAIL PROTECTED] others? Jean-Frederic Clere [EMAIL PROTECTED] mailing list/documentation comments: Pier Fumagalli [EMAIL PROTECTED] : 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. I love being quoted :) 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), There were some other motivations when it all started... Mod_JK was unmaintained, and nobody knew how to make it work. I didn't like its design and took out the experiences I had while working on mod_jserv and all those nifty ideas, and put them together (note: the WARP protocol is a derivate of AJPv21 which was supposed to be used on JServ.NEXT)... Pier -- I think that it's extremely foolish to name a server after the current U.S. President. B.W. Fitzpatrick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: jakarta-tomcat-connectors documentation/summaries
Ignacio J. Ortega [EMAIL PROTECTED] wrote: webapp web servers: apache 1.3 others? Apache2. I think they got IIS and iPlanet - don't know what level of support. When webapp got support for IIS? I think webapp has got a win32 build for apache, not IIS support AFAIK, Correct. And since the code was donated to support NSAPI, then it was abandoned (the guy who did it is not around anymore). I'm thinking about stripping it out and go for the eat our own dogfood vision, meaning, I don't care about anything else but Apache (and frankly ATM I don't care much about Apache 1.3 anymore as well, if someone volunteers to keep maintaining that code, well, he's more than welcome to) Pier could you teach we a little about webapp? What can I tell you about it? :) Pier -- I think that it's extremely foolish to name a server after the current U.S. President. B.W. Fitzpatrick -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
jakarta-tomcat-connectors documentation/summaries
A while back, I responded to Henri Gomez's email: We will create really soon webpages for jakarta-tomcat-connectors with an offer to summarize some of the recent discussion about the various connectors currently available for Tomcat. Not to write new docs, just summarize the existing docs and mailing list dicussions into a page with stuff like: for each connector: pointer to source, any existint docs brief (one line) summary of the idea behind it brief (one line) history underlying protocol, pointers to definition who's working on it stable/development versions of tomcat it works with standalone or front end webserver? which webservers? for each: status popularity ranking pointers to comments about it on mailing lists I need to do the research anyway, in order to decide which connectors to use, so I thought I'd offer to write it up. But ... I made the offer almost a month ago, and I wanted to double check that somebody hadn't gone out and done all the work in the meantime. So: Am I (hopefully :-) too late? Has anyone done this yet? If not, I wanted to get most of it done this weekend. -- Christopher St. John [EMAIL PROTECTED] DistribuTopia http://www.distributopia.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
