<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: A new way to look at networking</title>
	<atom:link href="http://www.coverfire.com/archives/2008/03/25/a-new-way-to-look-at-networking/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coverfire.com/archives/2008/03/25/a-new-way-to-look-at-networking/</link>
	<description>Thoughts and musings</description>
	<lastBuildDate>Sun, 15 Jan 2012 21:25:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mike Burrell</title>
		<link>http://www.coverfire.com/archives/2008/03/25/a-new-way-to-look-at-networking/comment-page-1/#comment-190014</link>
		<dc:creator>Mike Burrell</dc:creator>
		<pubDate>Wed, 26 Mar 2008 14:23:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.coverfire.com/archives/2008/03/25/a-new-way-to-look-at-networking/#comment-190014</guid>
		<description>If you&#039;ve ever looked at &lt;a href=&quot;http://freenetproject.org/&quot; rel=&quot;nofollow&quot;&gt;Freenet&lt;/a&gt;, the idea of identifying data there is very similar. Freenet aims for total anonymity, so you can&#039;t tag people or nodes, only data. Freenet is sort of a global namespace with the basic datum being the CHK (content hash key) where the &quot;filename&quot; (URL) is a hash of the data&#039;s contents. You gain local namespaces through a PKI.
I bring this up because I always thought it was a brilliant model for dealing with redundancy in, for example, the web. Any time any two people are requesting the same data, they&#039;re requesting the same file, even if they don&#039;t know it. This has great implications for caching. If web pages were more modular (e.g., a web page wasn&#039;t just one monolithic document, but composed of smaller documents) this would be even better: all of your static content could indeed be static.
Of course the problem with this sort of filesystem is the birthday paradox. I prefer to live in my dream world where hash collisions never happen ;)</description>
		<content:encoded><![CDATA[<p>If you&#8217;ve ever looked at <a href="http://freenetproject.org/" rel="nofollow">Freenet</a>, the idea of identifying data there is very similar. Freenet aims for total anonymity, so you can&#8217;t tag people or nodes, only data. Freenet is sort of a global namespace with the basic datum being the CHK (content hash key) where the &#8220;filename&#8221; (URL) is a hash of the data&#8217;s contents. You gain local namespaces through a PKI.<br />
I bring this up because I always thought it was a brilliant model for dealing with redundancy in, for example, the web. Any time any two people are requesting the same data, they&#8217;re requesting the same file, even if they don&#8217;t know it. This has great implications for caching. If web pages were more modular (e.g., a web page wasn&#8217;t just one monolithic document, but composed of smaller documents) this would be even better: all of your static content could indeed be static.<br />
Of course the problem with this sort of filesystem is the birthday paradox. I prefer to live in my dream world where hash collisions never happen ;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

