<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Calcium: feeding the Coral CDN with FeedTree</title>
	<link>http://feedtree.net/blog/2006/02/12/calcium/</link>
	<description>Releases, announcements, and information regarding the FeedTree software.</description>
	<pubDate>Tue, 13 May 2008 09:43:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Gary</title>
		<link>http://feedtree.net/blog/2006/02/12/calcium/#comment-10392</link>
		<pubDate>Sun, 18 Feb 2007 05:25:02 +0000</pubDate>
		<guid>http://feedtree.net/blog/2006/02/12/calcium/#comment-10392</guid>
					<description>This would also be very useful for maintaining an internal archive of links on one's website.

It could crawl your blog or site, cache anything you link to, and if those links ever go dead (or go paid), a visitor can click on the cached link instead.

Perhaps there's something out there like that, but I've not run across it yet...</description>
		<content:encoded><![CDATA[<p>This would also be very useful for maintaining an internal archive of links on one&#8217;s website.</p>
<p>It could crawl your blog or site, cache anything you link to, and if those links ever go dead (or go paid), a visitor can click on the cached link instead.</p>
<p>Perhaps there&#8217;s something out there like that, but I&#8217;ve not run across it yet&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: geek ramblings &#187; links for 2006-03-18</title>
		<link>http://feedtree.net/blog/2006/02/12/calcium/#comment-96</link>
		<pubDate>Sat, 18 Mar 2006 00:26:25 +0000</pubDate>
		<guid>http://feedtree.net/blog/2006/02/12/calcium/#comment-96</guid>
					<description>[...] the FeedTree weblog :: Archive :: Calcium: feeding the Coral CDN with FeedTree I once suggested to the Slashdot guys that they should do something like this. They could mitigate the Slashdot Effect somewhat by seeding the distributed cache, then link to the cached version of a page. As far as I know, they haven't done it, though. (tags: web cache caching coralcache feedtree digg slashdot) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the FeedTree weblog :: Archive :: Calcium: feeding the Coral CDN with FeedTree I once suggested to the Slashdot guys that they should do something like this. They could mitigate the Slashdot Effect somewhat by seeding the distributed cache, then link to the cached version of a page. As far as I know, they haven&#8217;t done it, though. (tags: web cache caching coralcache feedtree digg slashdot) [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: CVS Test Blog &#187; Daily Links</title>
		<link>http://feedtree.net/blog/2006/02/12/calcium/#comment-95</link>
		<pubDate>Fri, 17 Mar 2006 23:29:01 +0000</pubDate>
		<guid>http://feedtree.net/blog/2006/02/12/calcium/#comment-95</guid>
					<description>[...] the FeedTree weblog :: Archive :: Calcium: feeding the Coral CDN with FeedTree I once suggested to the Slashdot guys that they should do something like this. They could mitigate the Slashdot Effect somewhat by seeding the distributed cache, then link to the cached version of a page. As far as I know, they haven&amp;#8217;t done it, though. (tags: web cache caching coralcache feedtree digg slashdot) [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] the FeedTree weblog :: Archive :: Calcium: feeding the Coral CDN with FeedTree I once suggested to the Slashdot guys that they should do something like this. They could mitigate the Slashdot Effect somewhat by seeding the distributed cache, then link to the cached version of a page. As far as I know, they haven&#8217;t done it, though. (tags: web cache caching coralcache feedtree digg slashdot) [&#8230;]
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
