<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Vinogusto Blog</title>
	<link>http://www.vinogusto.com/blog/en</link>
	<description>What's new on Vinogusto.com ?</description>
	<pubDate>Tue, 13 May 2008 21:03:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>

	<item>
		<title>Comment on We optimised the code at server side &#038; client-browser side by Luis Peralta</title>
		<link>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-3</link>
		<author>Luis Peralta</author>
		<pubDate>Mon, 17 Sep 2007 16:40:03 +0000</pubDate>
		<guid>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-3</guid>
		<description>Hi jack,

  Yes, apache on linux. The htaccess file would be really helpful. Thanks in advance!</description>
		<content:encoded><![CDATA[<p>Hi jack,</p>
<p>  Yes, apache on linux. The htaccess file would be really helpful. Thanks in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We optimised the code at server side &#038; client-browser side by jack</title>
		<link>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-2</link>
		<author>jack</author>
		<pubDate>Fri, 14 Sep 2007 07:45:28 +0000</pubDate>
		<guid>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-2</guid>
		<description>Hi Luis,

We applied the 13 performance rules provided by Yahoo regarding the client-side code optimisation.

A. Etag :

If you look at the last § of the etag rule : "If you're not taking advantage of the flexible validation model that ETags provide, it's better to just remove the ETag altogether. The Last-Modified header validates based on the component's timestamp. And removing the ETag reduces the size of the HTTP headers in both the response and subsequent requests."... Etag are just not really needed (at least for vinogusto)... 

B. Deflate &#038; content-length

I observe that while gzip-deflate is active, the server provides the content-length header : 
Headers (provided by Firebug) : 
Content-Encoding gzip
Content-Length 6557
Keep-Alive timeout=15, max=100
Connection Keep-Alive

Are you using apache on Linux ? I can send you my htaccess config...

Hope this helps a bit. 

Regards,

jack</description>
		<content:encoded><![CDATA[<p>Hi Luis,</p>
<p>We applied the 13 performance rules provided by Yahoo regarding the client-side code optimisation.</p>
<p>A. Etag :</p>
<p>If you look at the last § of the etag rule : &#8220;If you&#8217;re not taking advantage of the flexible validation model that ETags provide, it&#8217;s better to just remove the ETag altogether. The Last-Modified header validates based on the component&#8217;s timestamp. And removing the ETag reduces the size of the HTTP headers in both the response and subsequent requests.&#8221;&#8230; Etag are just not really needed (at least for vinogusto)&#8230; </p>
<p>B. Deflate &#038; content-length</p>
<p>I observe that while gzip-deflate is active, the server provides the content-length header :<br />
Headers (provided by Firebug) :<br />
Content-Encoding gzip<br />
Content-Length 6557<br />
Keep-Alive timeout=15, max=100<br />
Connection Keep-Alive</p>
<p>Are you using apache on Linux ? I can send you my htaccess config&#8230;</p>
<p>Hope this helps a bit. </p>
<p>Regards,</p>
<p>jack</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We optimised the code at server side &#038; client-browser side by Luis Peralta</title>
		<link>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-1</link>
		<author>Luis Peralta</author>
		<pubDate>Wed, 12 Sep 2007 09:49:26 +0000</pubDate>
		<guid>http://www.vinogusto.com/blog/en/2007/21/we-optimised-the-code-at-server-side-client-browser-side/#comment-1</guid>
		<description>Hi,

  Just wondering why you disabled etag support as it is supposed to allow conditional fetching, as the expiration headers.

  Having tried the deflate module... doesn't it remove the content-length headers of your requests? That's what I encountered, suddenly losing keep-alive support as it requires that header to be present.

  Regards,</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>  Just wondering why you disabled etag support as it is supposed to allow conditional fetching, as the expiration headers.</p>
<p>  Having tried the deflate module&#8230; doesn&#8217;t it remove the content-length headers of your requests? That&#8217;s what I encountered, suddenly losing keep-alive support as it requires that header to be present.</p>
<p>  Regards,</p>
]]></content:encoded>
	</item>
</channel>
</rss>
