Even in the most dynamic sites, I can't imagine that you don't have gif's, jpg's or png's. Also, hopefully you have linked external stylesheets and perhaps some reuseable javascript that is in a separate file. These items usually are served on most every page because they are related to the header or footer or navigation elements.
AFAIK, this is where the advantage of a static page webserver or even a cache appliance comes in handy. Because you reduce the workload of the tomcat server to ~ONLY~ truly dynamic content. John -----Original Message----- From: David M. Karr [mailto:[EMAIL PROTECTED]] Sent: Monday, October 01, 2001 6:20 PM To: [EMAIL PROTECTED] Subject: Any reason to use Apache w/ Tomcat for webapp with all dynamic web pages? If you're committed to a project where virtually all of the pages will be dynamically generated, through JSP most likely, and you're committed to using Tomcat, is there ANY good reason to use Apache, in addition to Tomcat? I surveyed the FAQ, and I didn't notice this question being specifically addressed. AFAIU, Apache is good for serving static pages or resources. If you're only serving dynamic content, it only serves to complicate the deployment, and serves no useful purpose. Can anyone give me any opposing viewpoint, assuming a dynamic webapp with Tomcat? -- =================================================================== David M. Karr ; Best Consulting [EMAIL PROTECTED] ; Java/Unix/XML/C++/X ; BrainBench CJ12P (#12004)
