<?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: Mozilla Web Caching Summit</title>
	<atom:link href="http://ajaxian.com/archives/mozilla-web-caching-summit/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/mozilla-web-caching-summit</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: getify</title>
		<link>http://ajaxian.com/archives/mozilla-web-caching-summit/comment-page-1#comment-282666</link>
		<dc:creator>getify</dc:creator>
		<pubDate>Thu, 08 Apr 2010 11:42:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8869#comment-282666</guid>
		<description>I&#039;m wondering why &quot;prioritizing&quot; is seen as the issue... Do we think that browser caches are failing to be (fully) primed because the cache size is limited and older but more &quot;important&quot; stuff gets pushed out with newer less important stuff?</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering why &#8220;prioritizing&#8221; is seen as the issue&#8230; Do we think that browser caches are failing to be (fully) primed because the cache size is limited and older but more &#8220;important&#8221; stuff gets pushed out with newer less important stuff?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: yusufg</title>
		<link>http://ajaxian.com/archives/mozilla-web-caching-summit/comment-page-1#comment-282576</link>
		<dc:creator>yusufg</dc:creator>
		<pubDate>Thu, 08 Apr 2010 03:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8869#comment-282576</guid>
		<description>How about auto-scaling disk cache size based on size of the disk. Firefox still has a 50MB cache when disks are now coming in the 100+ GB sizes

I&#039;ve filed this bugzilla report a while ago

https://bugzilla.mozilla.org/show_bug.cgi?id=498076</description>
		<content:encoded><![CDATA[<p>How about auto-scaling disk cache size based on size of the disk. Firefox still has a 50MB cache when disks are now coming in the 100+ GB sizes</p>
<p>I&#8217;ve filed this bugzilla report a while ago</p>
<p><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=498076" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=498076</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jscripter</title>
		<link>http://ajaxian.com/archives/mozilla-web-caching-summit/comment-page-1#comment-282551</link>
		<dc:creator>jscripter</dc:creator>
		<pubDate>Wed, 07 Apr 2010 19:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8869#comment-282551</guid>
		<description>I had actually written an article on this subject, i hope it&#039;s of interest to anyone:

http://jeveloper.com/article/view/future-of-the-browser

Proposing that browser&#039;s cache engine looks up a cloud resource.

Take a &quot;read&quot; :)</description>
		<content:encoded><![CDATA[<p>I had actually written an article on this subject, i hope it&#8217;s of interest to anyone:</p>
<p><a href="http://jeveloper.com/article/view/future-of-the-browser" rel="nofollow">http://jeveloper.com/article/view/future-of-the-browser</a></p>
<p>Proposing that browser&#8217;s cache engine looks up a cloud resource.</p>
<p>Take a &#8220;read&#8221; :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: roblarsen</title>
		<link>http://ajaxian.com/archives/mozilla-web-caching-summit/comment-page-1#comment-282550</link>
		<dc:creator>roblarsen</dc:creator>
		<pubDate>Wed, 07 Apr 2010 18:28:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8869#comment-282550</guid>
		<description>I would like to see prioritization. For my sites, I would want CSS, JS and then interface images- in that order. With interface images I would key in on the main site sprite and then scale back priority from there.</description>
		<content:encoded><![CDATA[<p>I would like to see prioritization. For my sites, I would want CSS, JS and then interface images- in that order. With interface images I would key in on the main site sprite and then scale back priority from there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

