The client is responsible for asking the server for a GZiped version. The server will be looking for two things, the request is http 1.1, and a header of Accept-Encoding: gzip.An easy way to look for these headers is to use firebug IIS6 - GZip can be enabled with the iis snap-in. Microsofts MSDN Topic On Gzip With IIS6 IIS7 - GZip can be enabled with the web.
Config using httpCompression xml tag Nick Berardi's Getting IIS 7 to Compress JavaScript By minifying and packing javascript files, your decreasing the total size of JavaScript by removing whitespace and shortening your variables names.
Great walk-through for IIS6: engineering. Leads360. Com/post/9301650692/… – Bill Paetzke Aug 24 at 20:49.
My preferred way of doing this would be to using a compression tool like YUI Compressor and make it part of the build process (After minifying, the compression ratio won’t be so high. Or you can use both. Point being that you shouldn’t miss the greater performance problem given below).
One of the main problems with compression by IIS is that it doesn’t pack all the JS/CSS files into a single file. So if your site has 7 JS files and 20 CSS (surprisingly this is very common) it will take 27 HTTP round trip to get your data. Writing a HTTP handler to do this is a good idea for people with shared hosting.
A simple build algo would be to have a make file in the JS/CSS root directory If(build. Config == release) { Add your js file in order to the make files. E.g.JQuery.
Js jQuery.form. Js jQuery.container. Js custom.
Js Split and pass it as params to YUI Compress O/P to site. Js Delete all the above files. } In release mode you page master should only refer site.
Js Edit: Here's a link to get YUI and nant integrated. Edit: Justin Etheredge has released an awesome tool to combine and compress css/js file called SquishIt.
You could also use code to GZip the scripts. The way it works is that you use an ASP. NET page to deliver the compressed file along with the correct headers (telling the browser that this stream is compressed).
I've written an article how to utilize GZip compression along with minifying (using YUI) and bundling the scripts (less round trips to the server), you'll find it at codeproject.com/KBecause ustom-controls/smartinclude.aspx.
I second that IIS is the place to configure this. If you can't directly change IIS you can add a handler to all requests which checks for the Accept-Encoding: gzip or deflate settings. Then you do the right compression using something like SharpZipLib.
However this gets kludgey quickly. You will find some limited success in manually gzipping your static files like css or js. Say you include styles.css.
Gz and scripts.js. Gz in your html, and you map the gz extension to the mimetype for gzipped text (is it application/x-gzip? ) a lot of browsers (ie, firefox, safari, maybe chrome) will handle it just fine.
But some browsers won't, and you're leaving them out (links, maybe older opera).
I've been using a handy little server control for my CSS minification, called StyleManager. It uses YUI Compressor under-the-hood. It's easier to add to your site than adding YUI C manually, and its usage is a lot like asp.Net's ScriptManager, so it's quick to get used to.
Most importantly - it combines your CSS files too. So instead of having like 10 CSS files to download it'll just be 1, which will also be compressed etc.Check it out - gStyleManager.com.
My preferred way of doing this would be to using a compression tool like YUI Compressor and make it part of the build process (After minifying, the compression ratio won’t be so high. Or you can use both. Point being that you shouldn’t miss the greater performance problem given below).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.