This is an solution (kind of) to the issue I had with servelt filters.
Basically, don't use servlet filters for your gzip compression on the
server. Instead put apache in front of your web server and have apache
do your compression (as well has serving up static content).
Apache uses native c code which is faster and uses less resources than
Java.
Also Apache can be configured to switch compression settings based on
browser detected. Although this could be problematic for IE browsers
that are fully spoofing as Mozilla but then again, they should not be
doing that anyway :]
Regards,
T
shakah - 20 Jun 2005 19:30 GMT
> This is an solution (kind of) to the issue I had with servelt filters.
>
[quoted text clipped - 6 lines]
>
> [ ...lines snipped...]
You should verify your performance/resource assumptions in your
environment. For instance, we used to use an Apache 1.3+ => mod_webapp
=> Tomcat 4.x environment, but we saw an overhead of around 100 ms per
request as compared to just using Tomcat (so we dropped Apache from the
picture). YMMV, of course.