> do is provide compression. With the XCompress for ISA, compression is done > on the ISA server by our filter. OK, meaning that XCompress now is one of the ends, got it. > Q: What is the purpose/benefit of compressing at the firewall? > A: Well firewall compression might not be that interesting, unless you are > using your ISA server for a reverse proxy or forward proxy. > > Let's say your ISA is set up as a proxy server for the outbound Internet at > your Coporate headquarters in New York, and you have a WAN where your branch > office is in LA. The branch office connects via a partial frame via VPN to > coporate that provides outbound access. If you install XCompress for IIS in > NY, it will compress all the Internet responses from the outside, making the > partial frame faster, and the VPN encryption quicker. > > Or, you have a ISA server in front of your web server, as a > firewall/proxy/cache, and you want to compress that traffic before it leaves > your data center. Install XCompress for IIS, and the outbound traffic is > reduced and your bandwidth bills goes down. Did not think of either of those 2 scenerios. Too much going on right now. > Q: How will that speed up traffic or reduce bandwidth usage? > A: Is this question answer by the above? Yes. John Tolmachoff Engineer/Consultant/Owner eServices For You