Hi all, Has anyone implemented the compression filter contributed by Amy Roh from Sun to the Tomcat 4.0 "examples" Web application.? The filter automatically compresses the response output stream, improving bandwidth utilization.
As documented in Jason Hunter's article for javaworld: http://www.javaworld.com/javaworld/jw-06-2001/jw-0622-filters-p3.html "The strategy of the CompressionFilter class is to examine the request headers to determine if the client supports compression, and if so, wrap the response object with a custom response whose getOutputStream() and getWriter() methods have been customized to utilize a compressed output stream." I have it up and running in my development environment and haven't experienced any problems! Which is great! I want to feel confident prior to releasing my app to Production, that there aren't any known problems waiting for me. Has anyone experienced problems using it in production? Does the actual compression take too long for anyone? Did it prove to be a bottleneck for anyone? Basically have people found this compression filter to be beneficial or detrimental? I'm always looking for ways to improving bandwidth utilization. I'm just not sure what benefits the compression filter really give me - I searched the struts-users list and found little debate regarding this filter. TIA, Mike
