> From: Gregg D Bolinger [mailto:[EMAIL PROTECTED] > Subject: Tomcat Alone or tomcat+IIS/Apache > > I know that delivering static content with Apache/IIS is > preferred.
Urban myth, based primarily on older Tomcat versions that did not perform anywhere near as well as the current one. > But does that matter if every single request has > to go to Tomcat because the data is dynamic? Think about it: How could adding path length and latency for every request improve performance? > What is the benefit of Tomcat + Apache/IIS on major J2EE apps? Job security perhaps? Also increased stress levels, if you enjoy that sort of thing. Unless there's something specific for httpd or IIS to do (e.g., poor man's load balancing), simplify your life and leave them out. Check out Peter Lin's performance measurements for just static content, and you may decide you don't need httpd or IIS for that, either. http://jakarta.apache.org/tomcat/articles/benchmark_summary.pdf - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
