[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/10 03:57:48

Modified files:
        pointers       : article.rst 

Log message:
        Tighten CAW

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.184 
manuscripts/pointers/article.rst:1.185
--- manuscripts/pointers/article.rst:1.184      Mon Nov 10 03:50:54 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 03:57:47 2003
@@ -273,23 +273,24 @@
 
 A trivial approach to P2P versioning
 is to have a centralized server keep track of the current version
-of a document, such as in the *Content-Addressable Web* 
+of a document, as in the *Content-Addressable Web* 
 proposal [content-addressable-web]_, in which clients download 
 a file's hash through HTTP (using an HTTP URI),
-then download the file through, e.g., a filesharing network.
+and can then obtain
+the file through, e.g., a filesharing network.
 This provides some of the efficiency advantages of a P2P Web.
-However, there is still a single point of failure, and
-links still break when pages move to a different directory
-or Web server.
-In the Content-Addressable Web proposal, the situation
-regarding versioning is the same as on the current Web.
+However, there is still a single point of failure, the web server, and
+links still break when pages are moved to a different directory.
+
+..  In the Content-Addressable Web proposal, the situation
+    regarding versioning is the same as on the current Web.
 
 *Freenet*, a P2P network for anonymous publication [freenet-ieee]_,
 was originally planned to have an
 update mechanism where the network would remember
 the current version of a document, and update this information
-when receiving a message signed by the appropriate key,
-rather like in OceanStore. However, in practice,
+when receiving a message signed by the appropriate key.
+However, in practice,
 Freenet has a rather peculiar combination 
 of two workarounds [freenetfaq]_.
 In date-based updating, the URI for the current version