You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Ryan McDonough <ry...@rcn.com> on 2002/06/12 05:10:43 UTC

Choosing between mod_jk or mod_webapp?

I'm trying to help a client of mine choose between using mod_webapp or
mod_jk as their link between Tomcat and Apache. I have been successful in
getting both connectors to work, the question is which one is better? My gut
says mod_webapp is the way to go, but I haven't spent much time with it to
make a solid decision about it. I should mention some of my clients
requirements and concerns. As a requirement, they want Apache to handle
serving all non-JSP files such as images, html, javascripts, etc. They are
currently happy with mod_jk because they can configure like this:

JkMount /*.jsp ajp13

They like the idea that they an put JSP's in the doc root and tomcat will
only serve the JSP's. They are also running virtual hosts on Apache, and
they want the webapp to be mounted at the root of each virtual host. Their
concern is that if mod_webapp is used, HTML and image files will still be
served up by Tomcat, thus bringing into question if Apache is reducing the
server load on Tomcat.

I too am curious if mod_webapp uses Apache to server image and HTML files.
It does seem that mod_webapp is using Tomcat to serve everything, whereas
mod_jk seems to just handle servlets and JSP's. I know I can place an images
directory somewhere in Apache, but they also want to start using webapps to
deploy a complete module. So, in a nutshell, what connector is the best
choice? I would greatly appriciate any advice on this topic. Thanks.

Ryan-


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>