Basically, the idea is that if you want to serve static content along with dynamic (i.e., Tomcat webapp generated) content, you can server the dynamic through mod_jk/Tomcat and server the static from Apache. Apache tends to be more efficient and finely tunable from the straight http side.

Additionally, if you want to cluster Tomcat's, the JK module is essential.

So, if you only serve dynamic content and do not need clustering, let Tomcat servr the http connections. If you need to have Tomcat on another server (due to DMZ security, etc), use mod_proxy to pass all requests from Apache to the http connector of Tomcat.

Finally, if you have static content and/or need clustering, go with mod_jk.

Ben Ricker

On Jan 10, 2005, at 5:54 PM, Troy Simpson wrote:


Parsons...

How would mod_proxy() work?
How is it used?
I have not used it.

Thanks,
Troy

--
Troy Simpson
  Applications Analyst/Programmer, OCPDBA, MCSE, SCSA
North Carolina State University Libraries
Campus Box 7111 | Raleigh | North Carolina
ph.919.515.3855 | fax.919.513.3330

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to