If your traffic is going across the internet (or a corporate WAN) - then you
probably want to zip your output.

If your traffic is all LAN based - compression will probably not make much of
a difference.

Don't worry about writing a compression filter - tomcat comes with one on its
HTTP connector. Or if your using apache - use mod_gzip. I here the latest IIS
also has compression support.

-Tim

Ben Bookey wrote:
>
> Dear list,
>
> I have seen an example of using a filter, to Zip/compress the outgoing
> request.
> This for me is an exciting way of speeding up the load time for my webApp.
> ( For those who
> dont know, most internet browsers have an integrated unzip function, so a
> server can send
> the client a zipped html file, with the mime type set correctly and the
> browser will display the page, reducing
> drastically the bandwidth)
>
> i) Is this technique recommended at all ? could this lead to a bottleneck at
> the filter ?
>
> ii) IS this limited to html pages or graphics ? etc.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)