<?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: Towards Package-local Data</title>
	<atom:link href="http://news.qooxdoo.org/towards-package-local-data/feed" rel="self" type="application/rss+xml" />
	<link>http://news.qooxdoo.org/towards-package-local-data</link>
	<description>The qooxdoo news section</description>
	<lastBuildDate>Sun, 28 Feb 2010 13:47:38 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thomas Herchenröder</title>
		<link>http://news.qooxdoo.org/towards-package-local-data/comment-page-1#comment-12448</link>
		<dc:creator>Thomas Herchenröder</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://news.qooxdoo.org/?p=2518#comment-12448</guid>
		<description>@Sebastian It&#039;s a first whack at the issue, maybe we&#039;ll further adjust this. As I wrote in the post, it&#039;s not only about keeping packages at a certain size level. It&#039;s about keeping alternative parts separate, together with their resources. In the example with the themes, the packages with the theme classes alone were ultimately small (&lt;1kb), and would have merged easily into a larger package. But as they draw in a lot of resource info, this would have blown up the receiving package beyond 500kb. Blocking the private packages from merging kept each of them on an acceptable 120kb level eventually, and only one of them would be loaded at run time anyway. The others, amounting to about 360kb, could be left on disk.</description>
		<content:encoded><![CDATA[<p>@Sebastian It&#8217;s a first whack at the issue, maybe we&#8217;ll further adjust this. As I wrote in the post, it&#8217;s not only about keeping packages at a certain size level. It&#8217;s about keeping alternative parts separate, together with their resources. In the example with the themes, the packages with the theme classes alone were ultimately small (&lt;1kb), and would have merged easily into a larger package. But as they draw in a lot of resource info, this would have blown up the receiving package beyond 500kb. Blocking the private packages from merging kept each of them on an acceptable 120kb level eventually, and only one of them would be loaded at run time anyway. The others, amounting to about 360kb, could be left on disk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sebastian Werner</title>
		<link>http://news.qooxdoo.org/towards-package-local-data/comment-page-1#comment-12446</link>
		<dc:creator>Sebastian Werner</dc:creator>
		<pubDate>Fri, 06 Nov 2009 19:10:40 +0000</pubDate>
		<guid isPermaLink="false">http://news.qooxdoo.org/?p=2518#comment-12446</guid>
		<description>Interesting post. Just one question. Wouldn&#039;t it be more useful to have &quot;keep-private-packages-under&quot; : &quot;20kb&quot; instead of &quot;no-merge-private-package&quot;? Would be a little more flexible. Finally it makes no sense to create a 5KB JS file which is loaded separately, right?</description>
		<content:encoded><![CDATA[<p>Interesting post. Just one question. Wouldn&#8217;t it be more useful to have &#8220;keep-private-packages-under&#8221; : &#8220;20kb&#8221; instead of &#8220;no-merge-private-package&#8221;? Would be a little more flexible. Finally it makes no sense to create a 5KB JS file which is loaded separately, right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
