[Gzz-commits] manuscripts/pointers article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/11/06 07:53:40

Modified files:
        pointers       : article.rst 

Log message:
        Twids

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.144&tr2=1.145&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.144 
manuscripts/pointers/article.rst:1.145
--- manuscripts/pointers/article.rst:1.144      Thu Nov  6 02:54:57 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 07:53:38 2003
@@ -19,6 +19,9 @@
 However, filesharing systems don't allow documents
 to be updated.
 
+However, current P2P system do not provide adequate versioning
+because 
+
 We propose *pointer records*, 
 signed files containing a document's id, 
 its current version's hash, and a timestamp,
@@ -29,14 +32,14 @@
 implementing hash-based addressing. Using pointer records and the Storm
 data model, several P2P networks can be used interoperably
 as a P2P Web (except, naturally, for dynamically generated pages), 
-and web pages
-can have the same URI while residing on any host on any network.
+and all versions of a web page
+will have the same URI while residing on any host on any network.
 Past versions of a web page 
 remain accessible as long as anybody keeps a copy.
 
 We discuss our preliminary implementation
-as well as possible applications of pointer records
-and the Storm data model outside the P2P Web.
+as well as other possible applications of pointer records
+and the Storm data model.
 
 
 ..  This loses a major benefit of filesharing:
@@ -70,12 +73,12 @@
 If the Web worked like a filesharing system, there would be
 no central point of failure for a web page; a page could be downloaded
 from any host that has a copy. This would save bandwidth
-and increase availability. However, if the Web worked like
-a filesharing system, web pages could not be updated.
-Some filesharing systems offer permanent URIs for files 
-(e.g., [freenet-ieee-andalso-edonkey2kurl]_),
-based on the files' cryptographic hashes,
-which could be used for linking; but
+and increase availability. 
+Files could be
+linked using  permanent URIs based on the files' cryptographic 
+hashes, as in [freenet-ieee-andalso-edonkey2kurl]_.
+However, if the Web worked like
+a filesharing system, web pages could not be updated;
 a new version of a web page would have a different hash,
 and thus a different URI. [#update]_
 
@@ -83,7 +86,7 @@
    infeasible to update all pages linking to it, and thus
    all pages linking to *them*, and thus...
 
-There are some (non-filesharing) P2P systems 
+There are some non-filesharing P2P systems 
 that do offer an update mechanism. *CFS* [dabek01widearea]_
 is a file system based on Chord [stoica01chord]_, storing
 data in a distributed hashtable (DHT). CFS identifies