<?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: Update on Near Term Goals for TileCache</title>
	<atom:link href="http://crschmidt.net/blog/236/update-on-near-term-goals-for-tilecache/feed/" rel="self" type="application/rss+xml" />
	<link>http://crschmidt.net/blog/236/update-on-near-term-goals-for-tilecache/</link>
	<description>Ramblings of a GIS Hacker</description>
	<pubDate>Wed, 19 Nov 2008 11:27:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: crschmidt</title>
		<link>http://crschmidt.net/blog/236/update-on-near-term-goals-for-tilecache/#comment-18661</link>
		<dc:creator>crschmidt</dc:creator>
		<pubDate>Sat, 21 Jul 2007 12:38:24 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/236/update-on-near-term-goals-for-tilecache/#comment-18661</guid>
		<description>Pete -- 

Similar to all my TileCache setups, I treat caching as a secondary task, outside of TileCache's domain. Because most data is updated at regular intervals, it is far easier for the server admins to configure the caching than it would be to bake that functionality into TileCache. 

During testing, such caching would inappropriate, because the tiles that were there would have been changing regularly, and I didn't want to have to clear my browser cache every time I made a small change in the code.

I'm still not convinced that my code is at all right -- once I am, I'll change the demo to live on the main TileCache server that MetaCarta hosts -- so until that happens, I'm not adding caching headers because it makes my life more difficult, rather than for any other reason.</description>
		<content:encoded><![CDATA[<p>Pete &#8212; </p>
<p>Similar to all my TileCache setups, I treat caching as a secondary task, outside of TileCache&#8217;s domain. Because most data is updated at regular intervals, it is far easier for the server admins to configure the caching than it would be to bake that functionality into TileCache. </p>
<p>During testing, such caching would inappropriate, because the tiles that were there would have been changing regularly, and I didn&#8217;t want to have to clear my browser cache every time I made a small change in the code.</p>
<p>I&#8217;m still not convinced that my code is at all right &#8212; once I am, I&#8217;ll change the demo to live on the main TileCache server that MetaCarta hosts &#8212; so until that happens, I&#8217;m not adding caching headers because it makes my life more difficult, rather than for any other reason.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://crschmidt.net/blog/236/update-on-near-term-goals-for-tilecache/#comment-18660</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Fri, 20 Jul 2007 22:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://crschmidt.net/blog/archives/236/update-on-near-term-goals-for-tilecache/#comment-18660</guid>
		<description>It would help a lot if the tiles you return at that ArcIMS link, had a cache header set to they would be cached on the client browser. My browser is refetching the tiles making it much much slower and put a lot more load on your server.</description>
		<content:encoded><![CDATA[<p>It would help a lot if the tiles you return at that ArcIMS link, had a cache header set to they would be cached on the client browser. My browser is refetching the tiles making it much much slower and put a lot more load on your server.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
