While we do have Apache in the mix (for some legacy apps), we also run Squid [1] in reverse-proxy mode in front of *that* to (a) reduce response time on cachable content and (b) remove some of the load on Tomcat.
It did mean we had to be pretty careful about our HTTP cache-control headers, but it's been a nice solution.
dwh
[1] http://www.squid-cache.org/
Shapira, Yoav wrote:
This is a good example of something that hits on Apache's strong points:
perl, mod_php, rewriting. So it's probably good for you to use Apache.
But many people on this list come here because they work with servlets
and JSPs, and maybe some static content. In many of those cases, Apache
is not needed. And in no case should it be added without careful
thought and consideration, as it's a significant architecture piece.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
