| Re: [aus-dotnet] Http Compression... |
- From: Donald
- Subject: Re: [aus-dotnet] Http Compression...
- Date: Fri, 12 Aug 2005 00:33:30 +1000
- References:
- RE: [aus-dotnet] Http Compression..., Mick Badran
- Prev by Date: RE: [aus-dotnet] OT: tech ed
- Next by Date: Re: [aus-dotnet] C1 FlexGrid
- Previous by thread: RE: [aus-dotnet] Http Compression...
- Next by thread: [aus-dotnet] Deploying a .Net Architecture for User Authentication and Search
- Index(es):
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Stumbled Across this article tonight about IIS 5.0 Compression (if anyone is interested)
http://support.microsoft.com/?id=322603 - HOW TO: Enable ASPX Compression in IIS
SUMMARY
This step-by-step article describes how to configure Internet
Information Services (IIS) 5.0 to compress .aspx pages. To use .aspx pages, you
must have the ASP.NET page framework installed. You add the compression
functionality for .aspx files by editing the IIS metabase.
On 06/07/05, Mick Badran <mickb@xxxxxxxxxxxxxxxxxxxxx> wrote:
Donald - you champ!
From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of Donald
Sent: Tuesday, 5 July 2005 11:23 PM
To: dotnet@xxxxxxxxxxx
Subject: Re: [aus-dotnet] Http Compression...to answer part or your myth buster question go to one of the original IIS 3rd party compression tools Port80 at http://www.port80software.com/products/httpzip/httpcompression whilst there you can enter a URL and see the outcome.(or at least the potential of compression outcome).
On 05/07/05, Mick Badran <mickb@xxxxxxxxxxxxxxxxxxxxx> wrote:I know we keep talking about 'if you want to compress...then here it is...'BUT'...dont do it as CPU will increase etc etc etc.'Does anyone have any perf numbers on this? Happy just to see any (in case you guess...I'm hooked on 'Myth Busters' - how many things do they blow up!)(as I understand, the compression details came in IIS 4.0 + http standards when CPUs werent half the 'men' of what they are today)The reason why I'm curious is that under IIS - we get the IIS Compressed Files folder where our static/cached page output will live ready to be shot down over the wire.Given the huge gains of compressing text, this keeps the wire pretty lean.Any thoughts fellow mythbusters??
From: dotnet-owner@xxxxxxxxxxx [mailto: dotnet-owner@xxxxxxxxxxx] On Behalf Of Joseph Cooney
Sent: Tuesday, 5 July 2005 10:54 AM
To: dotnet@xxxxxxxxxxx
Subject: Re: [aus-dotnet] Http Compression...AFAIK Http Compression is just a matter of setting the appropriate parameter in the HTTP header http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html and then compressing the output stream in the manner which you've indicated in the header. It is not in any way limited to IIS 6. By doing this you're effectively trading off increased server CPU utilization and possibly increased latency for decreased network traffic.
Joseph
On 7/5/05, Donald <donald.w.chow@xxxxxxxxx> wrote:
The following link shows a good step by step method on how to turn on IIS 6.0 compression.
http://www.dotnetjunkies.com/HowTo/16267D49-4C6E-4063-AB12-853761D31E66.dcik
Don
On 05/07/05, list@xxxxxxxxxxxxxxx < list@xxxxxxxxxxxxxxx> wrote:Anyone have any free resources on http compression...did not realise that broswers support compression...I want to compress most of my pages in asp.net 1.1 if possible....AnthonyS
(Click here for more information on the aus-dotnet mailling list)
