<?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>Kommentare zu: Cache strategies for Google App Engine</title>
	<atom:link href="http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/</link>
	<description>Blog of the CloudMe Project by Moritz Petersen</description>
	<lastBuildDate>Sun, 27 Mar 2011 15:18:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Von: Moritz</title>
		<link>http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/comment-page-1/#comment-161</link>
		<dc:creator>Moritz</dc:creator>
		<pubDate>Wed, 17 Mar 2010 19:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cloudme.org/?p=79#comment-161</guid>
		<description>So far, my application works quite good and there are only few over quota exceptions, so I haven&#039;t looked at task queues yet… 
Why do I want to have the cache built up lazily? That&#039;s because I believe that I have a better control about the thumbnail creation process that way and don&#039;t need to worry about if a thumbnail was created or not. If I were storing thumbnails only in DB, then I had to handle errors with some custom retry mechanism or a combination of all sort of methods (including the one described in the post). So I decided to go with the simple solution.</description>
		<content:encoded><![CDATA[<p>So far, my application works quite good and there are only few over quota exceptions, so I haven&#8217;t looked at task queues yet…<br />
Why do I want to have the cache built up lazily? That&#8217;s because I believe that I have a better control about the thumbnail creation process that way and don&#8217;t need to worry about if a thumbnail was created or not. If I were storing thumbnails only in DB, then I had to handle errors with some custom retry mechanism or a combination of all sort of methods (including the one described in the post). So I decided to go with the simple solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Simon Luijk</title>
		<link>http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/comment-page-1/#comment-160</link>
		<dc:creator>Simon Luijk</dc:creator>
		<pubDate>Wed, 17 Mar 2010 19:18:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cloudme.org/?p=79#comment-160</guid>
		<description>The task queue tasks are also killed at 30 seconds. You will have to break the task into smaller chunks. How about generating the thumbs when they are uploaded.</description>
		<content:encoded><![CDATA[<p>The task queue tasks are also killed at 30 seconds. You will have to break the task into smaller chunks. How about generating the thumbs when they are uploaded.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Moritz</title>
		<link>http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/comment-page-1/#comment-96</link>
		<dc:creator>Moritz</dc:creator>
		<pubDate>Mon, 15 Feb 2010 11:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cloudme.org/?p=79#comment-96</guid>
		<description>That is another good idea. However, I also like to reduce the number of datastore queries, and decided for memcache instead. I&#039;m using a scheduled task to refresh the cache, but haven&#039;t looked at the task queue API yet.

There are two problems I&#039;m dealing with when generating thumbnails: (1) The images service gets over quota quite quickly and (2) the scheduled task I&#039;ve written so far (and which is using a brute-force approach) gets killed after 30 seconds. Maybe a task queue is a better solution.</description>
		<content:encoded><![CDATA[<p>That is another good idea. However, I also like to reduce the number of datastore queries, and decided for memcache instead. I&#8217;m using a scheduled task to refresh the cache, but haven&#8217;t looked at the task queue API yet.</p>
<p>There are two problems I&#8217;m dealing with when generating thumbnails: (1) The images service gets over quota quite quickly and (2) the scheduled task I&#8217;ve written so far (and which is using a brute-force approach) gets killed after 30 seconds. Maybe a task queue is a better solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Rusty Wright</title>
		<link>http://blog.cloudme.org/2010/02/cache-strategies-for-google-app-engine/comment-page-1/#comment-95</link>
		<dc:creator>Rusty Wright</dc:creator>
		<pubDate>Sun, 14 Feb 2010 22:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.cloudme.org/?p=79#comment-95</guid>
		<description>Are you generating the thumbnails every time the page with a thumbnail is requested?  If so, instead, why not store the thumbnails in the GAE data store?  You could generate the thumbnails using the GAE task queue.</description>
		<content:encoded><![CDATA[<p>Are you generating the thumbnails every time the page with a thumbnail is requested?  If so, instead, why not store the thumbnails in the GAE data store?  You could generate the thumbnails using the GAE task queue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

