Hi Mark, I'll tell you about our experience. I made a public website for a real estate banner (franchiser). The public website gets over 3 million hits per day, and as you may imagine, lots of the bandwidth that gets consumed is images. So for that we have an Apache server which handles static content and delegates JSP pages to Tomcat. This setup works pretty well, but we're starting to reach the maximum capability, so we're switching to using load balanced tomcat servers. Here's the notes I wrote when doing the setup: www.ubeans.com/tomcat
On the other hand, I also made a webmail system for their 2000 agents. This system runs fine on a standalone tomcat running on a cheap PC. I guess if you expect to be serving lots of static content on a T-1 line you should seriously consider using Apache. Besides, it's not much harder or costlier to setup both. My 2 cents. Best Regards, Pascal Forget >Hi all. > >I know it's standard practice to hook Tomcat up to a webserver, but is >this really necessary? According to the docs, the main reason for this >is that Tomcat's performance when serving static files is sub-par, >although it usually goes on to note that this has improved recently. I >can't seem to find anything on Tomcat 4.0x though, and I'm wondering if >this advice is outdated? I thinking of using Tomcat only on a >production system with light to moderate traffic. Almost all pages are >JSP's, so the only static content would be images. > >So: What's the word on running Tomcat 4.02 without a webserver? What >does using Apache+Tomcat buy me? > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
