<?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"
	>
<channel>
	<title>Comments on: GWT Image.prefetch memory leak and suggestions for improvement</title>
	<atom:link href="http://www.pathf.com/blogs/2008/01/gwt-imageprefet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/01/gwt-imageprefet/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Thu, 08 Jan 2009 19:04:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Harold Campbell</title>
		<link>http://www.pathf.com/blogs/2008/01/gwt-imageprefet/#comment-3135</link>
		<dc:creator>Harold Campbell</dc:creator>
		<pubDate>Sun, 24 Aug 2008 03:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=104#comment-3135</guid>
		<description>Good point. I had noticed the same thing. I still don't like the fact that I must explicitly call the release. I think the framework should be smart enough to GC the images in the prefetchImages HashMap</description>
		<content:encoded><![CDATA[<p>Good point. I had noticed the same thing. I still don&#8217;t like the fact that I must explicitly call the release. I think the framework should be smart enough to GC the images in the prefetchImages HashMap</p>
]]></content:encoded>
	</item>
</channel>
</rss>
