<?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: Velocity: Forcing Gzip Compression</title>
	<atom:link href="http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/</link>
	<description>Essential knowledge for making your web pages faster.</description>
	<lastBuildDate>Sat, 04 Feb 2012 09:46:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Miles</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-3331</link>
		<dc:creator>Miles</dc:creator>
		<pubDate>Wed, 15 Jun 2011 16:46:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-3331</guid>
		<description>Along the same lines as Nicolas, is there a distinct need for the iframe?  That is, instead of an iframe, could an always compressed javascript src be served?</description>
		<content:encoded><![CDATA[<p>Along the same lines as Nicolas, is there a distinct need for the iframe?  That is, instead of an iframe, could an always compressed javascript src be served?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Grekas</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2663</link>
		<dc:creator>Nicolas Grekas</dc:creator>
		<pubDate>Tue, 09 Nov 2010 20:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2663</guid>
		<description>Oups, try again:

{{?php

if (isset($_GET[&#039;i&#039;])):

  header(&#039;Content-Encoding: deflate&#039;);

  // A base64 encoded transparent 1x1 GIF
  $img = &#039;R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==&#039;;

  echo gzdeflate(base64_decode($img));

else: ?}}

  {{script}}
  a = new Image;
  a.onload  = function(){alert(&#039;OK&#039;);};
  a.onerror = function(){alert(&#039;KO&#039;);};
  a.src = &#039;{{?php echo basename(__FILE__);?}}?i=1&#039;;
  {{/script}}

{{?php endif;?}}</description>
		<content:encoded><![CDATA[<p>Oups, try again:</p>
<p>{{?php</p>
<p>if (isset($_GET['i'])):</p>
<p>  header(&#8216;Content-Encoding: deflate&#8217;);</p>
<p>  // A base64 encoded transparent 1&#215;1 GIF<br />
  $img = &#8216;R0lGODlhAQABAIAAAP///wAAACH5BAEAAAAALAAAAAABAAEAAAICRAEAOw==&#8217;;</p>
<p>  echo gzdeflate(base64_decode($img));</p>
<p>else: ?}}</p>
<p>  {{script}}<br />
  a = new Image;<br />
  a.onload  = function(){alert(&#8216;OK&#8217;);};<br />
  a.onerror = function(){alert(&#8216;KO&#8217;);};<br />
  a.src = &#8216;{{?php echo basename(__FILE__);?}}?i=1&#8242;;<br />
  {{/script}}</p>
<p>{{?php endif;?}}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Grekas</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2662</link>
		<dc:creator>Nicolas Grekas</dc:creator>
		<pubDate>Tue, 09 Nov 2010 20:48:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2662</guid>
		<description>Even if it&#039;s useless, browser do support compressed images. I tested the PHP code below and it works perfectly. So we could replace your iframe with this - if it&#039;s an enhancement of course (it works on my local setup, that&#039;s all I know right now :) )



  
  a = new Image;
  a.onload  = function(){alert(&#039;OK&#039;);};
  a.onerror = function(){alert(&#039;KO&#039;);};
  a.src = &#039;?i=1&#039;;
  

</description>
		<content:encoded><![CDATA[<p>Even if it&#8217;s useless, browser do support compressed images. I tested the PHP code below and it works perfectly. So we could replace your iframe with this &#8211; if it&#8217;s an enhancement of course (it works on my local setup, that&#8217;s all I know right now :) )</p>
<p>  a = new Image;<br />
  a.onload  = function(){alert(&#8216;OK&#8217;);};<br />
  a.onerror = function(){alert(&#8216;KO&#8217;);};<br />
  a.src = &#8216;?i=1&#8242;;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Souders</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2660</link>
		<dc:creator>Steve Souders</dc:creator>
		<pubDate>Tue, 09 Nov 2010 18:27:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2660</guid>
		<description>@Nicolas: Images aren&#039;t compressed so it doesn&#039;t test the browser&#039;s ability to handle compressed content.</description>
		<content:encoded><![CDATA[<p>@Nicolas: Images aren&#8217;t compressed so it doesn&#8217;t test the browser&#8217;s ability to handle compressed content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nicolas Grekas</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2659</link>
		<dc:creator>Nicolas Grekas</dc:creator>
		<pubDate>Tue, 09 Nov 2010 13:23:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2659</guid>
		<description>What about using an image rather than an iframe ?

I mean :
a = new Image;
a.onload = function(){...}
a.src = &#039;gzipped-blank-image&#039;

I tested it on my local host and it seems to works equally well. Have you some data about iframe vs Image ?

Image seems much simpler to me, because iframe needs special code to prevent a loading bar, needs expensive DOM usage, etc.

Any though about this?</description>
		<content:encoded><![CDATA[<p>What about using an image rather than an iframe ?</p>
<p>I mean :<br />
a = new Image;<br />
a.onload = function(){&#8230;}<br />
a.src = &#8216;gzipped-blank-image&#8217;</p>
<p>I tested it on my local host and it seems to works equally well. Have you some data about iframe vs Image ?</p>
<p>Image seems much simpler to me, because iframe needs special code to prevent a loading bar, needs expensive DOM usage, etc.</p>
<p>Any though about this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Souders</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2273</link>
		<dc:creator>Steve Souders</dc:creator>
		<pubDate>Thu, 19 Aug 2010 18:15:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2273</guid>
		<description>@Shannon: Andy&#039;s preso does not mention what percentage of users were able to receive forced compression. If the test says 3-4%, that might be it for your audience.</description>
		<content:encoded><![CDATA[<p>@Shannon: Andy&#8217;s preso does not mention what percentage of users were able to receive forced compression. If the test says 3-4%, that might be it for your audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon Zhang</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2272</link>
		<dc:creator>Shannon Zhang</dc:creator>
		<pubDate>Thu, 19 Aug 2010 05:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2272</guid>
		<description>Hi Steve, 

On a daily basis, we see about 10% of the traffic does not have accept-encoding set on our website. We&#039;ve implemented the force gzip compression after listening to the velocity talk. It is such clever idea, our implementation is working in production, but for some reason we are only able to sent back compressed content to less than 3% of the requests, definitely not as much as what google is able to. In fact, we still have more than 3-4% that does not accept gzip compression but had the test. Any suggestions on why we are getting such low rate with this feature? Is it possible with the way our test servlet is done?</description>
		<content:encoded><![CDATA[<p>Hi Steve, </p>
<p>On a daily basis, we see about 10% of the traffic does not have accept-encoding set on our website. We&#8217;ve implemented the force gzip compression after listening to the velocity talk. It is such clever idea, our implementation is working in production, but for some reason we are only able to sent back compressed content to less than 3% of the requests, definitely not as much as what google is able to. In fact, we still have more than 3-4% that does not accept gzip compression but had the test. Any suggestions on why we are getting such low rate with this feature? Is it possible with the way our test servlet is done?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2258</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 05 Aug 2010 10:40:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2258</guid>
		<description>Just a thought:

Might it be possible to dynamically inject the script into the document by conditionally &#039;chunking&#039; it to the end, and thus removing the need for an additional call and iFrame?

Or am I missing the mark?</description>
		<content:encoded><![CDATA[<p>Just a thought:</p>
<p>Might it be possible to dynamically inject the script into the document by conditionally &#8216;chunking&#8217; it to the end, and thus removing the need for an additional call and iFrame?</p>
<p>Or am I missing the mark?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yoav Weiss</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2197</link>
		<dc:creator>Yoav Weiss</dc:creator>
		<pubDate>Wed, 14 Jul 2010 07:13:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2197</guid>
		<description>I suspect that the natural response from intermediary proxy authors would be (at least in the short term) to send out &quot;Accept-Encoding: identity&quot; header in the requests, making it non-standard to send forced GZIP responses. It would be a lot more simple for them to implement it then decompressing the responses.</description>
		<content:encoded><![CDATA[<p>I suspect that the natural response from intermediary proxy authors would be (at least in the short term) to send out &#8220;Accept-Encoding: identity&#8221; header in the requests, making it non-standard to send forced GZIP responses. It would be a lot more simple for them to implement it then decompressing the responses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt</title>
		<link>http://www.stevesouders.com/blog/2010/07/12/velocity-forcing-gzip-compression/#comment-2196</link>
		<dc:creator>Matt</dc:creator>
		<pubDate>Wed, 14 Jul 2010 04:07:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.stevesouders.com/blog/?p=1412#comment-2196</guid>
		<description>This is now a WordPress plugin (first comment):

http://wpdevel.wordpress.com/2010/07/13/forcing-gzip-httpwww-stevesouders-co/</description>
		<content:encoded><![CDATA[<p>This is now a WordPress plugin (first comment):</p>
<p><a href="http://wpdevel.wordpress.com/2010/07/13/forcing-gzip-httpwww-stevesouders-co/" rel="nofollow">http://wpdevel.wordpress.com/2010/07/13/forcing-gzip-httpwww-stevesouders-co/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

