>From a earlier post of mine: (Hasn't made it to
http://mikal.org/interests/java/tomcat/ by now)
mod_jk successor of mod_jserv
- Currently the best (At least that's what I sample
from the traffic in this list) connector for apache
mod_jk2 successor of mod_jk
- currently in alpha or beta state
AFAIK this development branch was induced through
the release of apache 2.
mod_webapp
- Was intended as a replacement for mod_jk
in tomcat 4. It's a complete redisign.
As it wasn't ready when tomcat 4 was released
mod_jk has been changed to allow an integration
with tomcat 4. Although mod_webapp seams to have
reached a state where it's close to production
quality it has some drawbags, so people like to
continue to use mod_jk. From what I see in this
list the development of mod_jk is more active
than mod_webapp.
http connector
It enables tomcat to act as a webserver standalone
coyote
The new HTTP Connector, currently in beta state
When it comes to documentation all connectors are
more or less undocumented about the inner features,
I know only docs that show you how to use them, but
none that allows you to decide which to use.
> -----Urspr�ngliche Nachricht-----
> Von: Peter T. Abplanalp [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 3. Juli 2002 23:01
> An: [EMAIL PROTECTED]
> Betreff: mod_jk v. mod_webapp v. ???
>
> hi all. i've gone through the list archives and googled for mod_jk
> and mod_webapp documentation and found that little exists but i did
> find some; however, i didn't find what i was looking for, namely why
> should one choose mod_jk over mod_webapp or vice versa? perhaps there
> is no difference. i did read something about mod_webapp just passing
> *all* requests for certain patterns to tomcat but i could not find if
> mod_jk behaved differently or not.
>
> actually, one more things comes to mind. is coyote a replacement/new
> name for mod_jk or is it a distinct connector?
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
