<?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: OSCON 2006: Ajax Optimization Techniques</title>
	<atom:link href="http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sat, 07 Nov 2009 23:35:20 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dave Grijalva</title>
		<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/comment-page-1/#comment-41102</link>
		<dc:creator>Dave Grijalva</dc:creator>
		<pubDate>Fri, 28 Jul 2006 23:46:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1650#comment-41102</guid>
		<description>One key thing to think about with jumbling all your files together is the ballance between the number of files and the amount of redundant code sent to the client.  For an application like flickr, every view has code that&#039;s specific to it.  It makes sense to bundle as much code as possible into a single file, but anything that&#039;s page specific should be left out.

The goal is to minimize load times (especially of the first page) by intelligently grouping blocks of code into single files, making smart use of caching, and not sending the client view specific code until they need it.</description>
		<content:encoded><![CDATA[<p>One key thing to think about with jumbling all your files together is the ballance between the number of files and the amount of redundant code sent to the client.  For an application like flickr, every view has code that&#8217;s specific to it.  It makes sense to bundle as much code as possible into a single file, but anything that&#8217;s page specific should be left out.</p>
<p>The goal is to minimize load times (especially of the first page) by intelligently grouping blocks of code into single files, making smart use of caching, and not sending the client view specific code until they need it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: z0s0</title>
		<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/comment-page-1/#comment-40937</link>
		<dc:creator>z0s0</dc:creator>
		<pubDate>Fri, 28 Jul 2006 00:15:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1650#comment-40937</guid>
		<description>Packaging up your JS files into a single bundle is &lt;strong&gt;a really good&lt;/strong&gt; idea.  I&#039;ve seen a massive increase in load speed by doing so. Firefox seems to only display the page once all the JavaScript is loaded, which contributes to the importance of this.

Interestingly Cal from Flickr &lt;a href=&quot;http://www.thinkvitamin.com/features/webapps/serving-javascript-fast&quot; rel=&quot;nofollow&quot;&gt;wrote a great article&lt;/a&gt; about this, and yet Flickr has no less than &lt;strong&gt;17&lt;/strong&gt; (!!) seperate .JS includes on the home page alone. Little wonder Flickr feels so slow to me.</description>
		<content:encoded><![CDATA[<p>Packaging up your JS files into a single bundle is <strong>a really good</strong> idea.  I&#8217;ve seen a massive increase in load speed by doing so. Firefox seems to only display the page once all the JavaScript is loaded, which contributes to the importance of this.</p>
<p>Interestingly Cal from Flickr <a href="http://www.thinkvitamin.com/features/webapps/serving-javascript-fast" rel="nofollow">wrote a great article</a> about this, and yet Flickr has no less than <strong>17</strong> (!!) seperate .JS includes on the home page alone. Little wonder Flickr feels so slow to me.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Rangi Keen</title>
		<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/comment-page-1/#comment-40896</link>
		<dc:creator>Rangi Keen</dc:creator>
		<pubDate>Thu, 27 Jul 2006 18:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1650#comment-40896</guid>
		<description>Another tool that is worth checking out is Fiddler (available at http://www.fiddlertool.com/). It integrates nicely with IE, but can work as a proxy for any browser. It gives you feedback similar to TamperData and includes a pie chart for the various MIME types (HTML, JS, CSS, etc) comprising a list of requests.</description>
		<content:encoded><![CDATA[<p>Another tool that is worth checking out is Fiddler (available at <a href="http://www.fiddlertool.com/)" rel="nofollow">http://www.fiddlertool.com/)</a>. It integrates nicely with IE, but can work as a proxy for any browser. It gives you feedback similar to TamperData and includes a pie chart for the various MIME types (HTML, JS, CSS, etc) comprising a list of requests.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Delusional Media &#187; OSCON 2006: Ajax Optimization Techniques</title>
		<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/comment-page-1/#comment-40878</link>
		<dc:creator>Delusional Media &#187; OSCON 2006: Ajax Optimization Techniques</dc:creator>
		<pubDate>Thu, 27 Jul 2006 15:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1650#comment-40878</guid>
		<description>[...] More Here [...]</description>
		<content:encoded><![CDATA[<p>[...] More Here [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Ajaxian &#187; Ajax Optimization Techniques Talk (OSCON 2006)</title>
		<link>http://www.sitepoint.com/blogs/2006/07/27/oscon-2006-ajax-optimization-techniques/comment-page-1/#comment-40846</link>
		<dc:creator>Ajaxian &#187; Ajax Optimization Techniques Talk (OSCON 2006)</dc:creator>
		<pubDate>Thu, 27 Jul 2006 12:46:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/?p=1650#comment-40846</guid>
		<description>[...] On the SitePoint Blogs today, &#8220;live&#8221; from this year&#8217;s OSCON, there&#8217;s a new post covering the talk from Kevin Henrikson concerning how to squeeze the most out of your Ajax connections - a few handy optimization techniques.   Kevin Henrikson of Zimbra gave a brisk presentation covering some of the lessons his organization has learned and the “dirty tricks” it has implemented to improve the performance of web applications that rely on large JavaScript/CSS codebases. Here’s a quick run-down of the items he covered. The slides of the talk are up on the Zimbra blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] On the SitePoint Blogs today, &#8220;live&#8221; from this year&#8217;s OSCON, there&#8217;s a new post covering the talk from Kevin Henrikson concerning how to squeeze the most out of your Ajax connections &#8211; a few handy optimization techniques.   Kevin Henrikson of Zimbra gave a brisk presentation covering some of the lessons his organization has learned and the “dirty tricks” it has implemented to improve the performance of web applications that rely on large JavaScript/CSS codebases. Here’s a quick run-down of the items he covered. The slides of the talk are up on the Zimbra blog. [...]</p>]]></content:encoded>
	</item>
</channel>
</rss>
