Hi, >I use Apache in front of Tomcat a long ago and see no >problems? BTW, Apache executes all static content, >such as image files. Why you don't recommend Apache?
Again, that's not what I said. You just have to evaluate your requirements carefully. Various factors like the content mix (%static vs. %dynamic), scalability requirements, SSL load, and others all figure into this decision. For better or worse, the connectors between Apache and Tomcat not always easy to set up. It's by far the most common question/problem reported on this list. But part of the reason it's such a common topic is because more people are using it than should be. Not coincidentally, many of these people are ones who read somewhere once that tomcat is not a production-quality HTTP server, or that you have to put Apache in front for production installations, and didn't bother to verify/confirm/benchmark this assertion before following it blindly. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
