Messages
Reply
Edit
Delete12:05 pm
3RI0PXGLN
| From: | Doug Dodge |
| To: | Rick Strahl |
OK, cool, thanks for the additional insight/information. Makes sense.
Doug
The big problem is that you can't control what get compressed. IIS chooses.
In general dynamic content compression can be very inefficient and adds extra overhead to the server. It also adds extra caching pressure on the server as it tries to cache content it compresses more aggressively.
IMHO, it's best to compress selected content that requires it (ie. large document output) from within the code that renders it. If you use ASP.NET this is very easy:
http://www.west-wind.com/weblog/posts/2007/Feb/05/More-on-GZip-compression-with-ASPNET-Content
In Web Connection it's actually even easier:
Response.GZipCompression = .T.
which you can do either on each request or globally for an entire process class.
+++ Rick ---
Hi Rick,
Have you ever written a blog on why this is? The reason I ask is that I'm standing up two test servers inside of a hyper-v setup. I had turned that feature on. Just curious to know why you aren't fond of it. Maybe an article somewhere you know of?
Thanks,
Doug
No Web Connection uses zlib to compress content.
IIS Dynamic Content Compression is something that happens automatically in IIS if enabled - basically it tries to compress any candidate traffic in IIS that qualifies. In general I don't like that module and keep the option disabled.
If you install IIS you do want to enable *Static* compression but not dynamic compression.
+++ Rick ---
Hi all,
I was just trying to diagnose a new IIS app event (concerning static compression temp folders, but that's not my question), when I noticed a message in IIS Manager "The dynamic content compression module is not installed." This is IIS7 on Win 2008 server (64 bit).
Question is, does WWWC need this module to be installed to use its GZip capabilities? I would like to start compressing large application/JSON dynamic responses.
Thanks.
Randy