JK2 and mod_jk have load balancing and really cool stuff like that. It's
more the direction things are going. It also loadbalances across
different machines.
mod_webapp was designed for a single machine using the WARP protocol.
>From the name you can tell is was designed to be fast. And it is.
I use mod_jk in production for Tomcat 4. No problems here...haven't found
an overriding reason here to switch to mod_jk2. If it ain't broke, don't
fix it. :)
John
On Tue, 8 Jul 2003 21:23:57 -0500 (CDT), <[EMAIL PROTECTED]> wrote:
I am getting ready to deploy Tomcat and Apache in a productio
I use mod_jk on my production servers. mod_jk2 has the best support for
advanced features (e.g. jni-channel, uni-channel, regexp mapping). If you
need them, then that is the only way to go (I don't need them, personally).
There isn't much (if any) developer support currently for mod_webapp, so b
I am getting ready to deploy Tomcat and Apache in a production
environment. What is the recommended way to go as far as the connectors
go? mod_webapp, mod_jk2 or mod_jk? I have used mod_webapp in the past
but was told that is not being used and that mod_jk2 is the way to go. I
want to hear
