<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Major sites not conserving bandwidth with gzip content compression</title>
	<atom:link href="http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression/feed" rel="self" type="application/rss+xml" />
	<link>http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression</link>
	<description>Anecdotes on Java, Ruby, Sysadmin, SEO, Design, and Management</description>
	<pubDate>Tue, 06 Jan 2009 09:32:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Aleksey Gopachenko</title>
		<link>http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression/comment-page-1#comment-2960</link>
		<dc:creator>Aleksey Gopachenko</dc:creator>
		<pubDate>Thu, 06 Jul 2006 08:11:17 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression#comment-2960</guid>
		<description>Your site may not have problems noticeable to users. But you comparing with "Web 2.0" site - and I have quite a practical expirience in this area - gzipped JS and gzip + XHR is a bad idea in IE. Also IE will not cache gzipped content under some (not so rare) conditions, thus effectively diabling you from any traffic "savings". You probably may carefully design Web 2.0 site with gzip compression in mind... but I don't really see why. 
While my first page is ~200k with 80% of that is library code (dojo), further updates range from 100 to 2000 bytes. System *feels* very responsive even through very slow connections. And the session traffic from typical user is about 10 to 80 times less.</description>
		<content:encoded><![CDATA[<p>Your site may not have problems noticeable to users. But you comparing with &#8220;Web 2.0&#8243; site - and I have quite a practical expirience in this area - gzipped JS and gzip + XHR is a bad idea in IE. Also IE will not cache gzipped content under some (not so rare) conditions, thus effectively diabling you from any traffic &#8220;savings&#8221;. You probably may carefully design Web 2.0 site with gzip compression in mind&#8230; but I don&#8217;t really see why.<br />
While my first page is ~200k with 80% of that is library code (dojo), further updates range from 100 to 2000 bytes. System *feels* very responsive even through very slow connections. And the session traffic from typical user is about 10 to 80 times less.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Huss</title>
		<link>http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression/comment-page-1#comment-2913</link>
		<dc:creator>Todd Huss</dc:creator>
		<pubDate>Wed, 05 Jul 2006 15:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression#comment-2913</guid>
		<description>Hi Aleksey, while there have been some bugs with Internet Explorer and compression in the past we haven't seen any issues with it. 

We have several million unique users a month that complain when things break and so far not a peep. Also, with massive sites like CNN, Slashdot, and MySpace doing compression, I'm hard pressed to accept the argument that compression introduces major problems for IE users.</description>
		<content:encoded><![CDATA[<p>Hi Aleksey, while there have been some bugs with Internet Explorer and compression in the past we haven&#8217;t seen any issues with it. </p>
<p>We have several million unique users a month that complain when things break and so far not a peep. Also, with massive sites like CNN, Slashdot, and MySpace doing compression, I&#8217;m hard pressed to accept the argument that compression introduces major problems for IE users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aleksey Gopachenko</title>
		<link>http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression/comment-page-1#comment-2892</link>
		<dc:creator>Aleksey Gopachenko</dc:creator>
		<pubDate>Tue, 04 Jul 2006 22:15:45 +0000</pubDate>
		<guid isPermaLink="false">http://gabrito.com/post/major-sites-not-conserving-bandwidth-with-gzip-content-compression#comment-2892</guid>
		<description>The problem is that IE (dominating browser) handles gzip *really* badly (no caching, errors).</description>
		<content:encoded><![CDATA[<p>The problem is that IE (dominating browser) handles gzip *really* badly (no caching, errors).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
