[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/10 06:54:30

Modified files:
        pointers       : article.rst 

Log message:
        twid related work

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.214 
manuscripts/pointers/article.rst:1.215
--- manuscripts/pointers/article.rst:1.214      Mon Nov 10 06:35:49 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 06:54:30 2003
@@ -269,15 +269,15 @@
 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, the web server, and
-links still break when pages are moved to a different directory.
+However, there is still a single point of failure
+for each page, 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
-destructive update mechanism.
+was originally planned to have a destructive update mechanism.
 However, in practice,
 Freenet currently uses a rather peculiar combination 
 of two workarounds [freenetfaq]_.
@@ -303,21 +303,23 @@
 is a file system based on Chord [stoica01chord]_, storing
 data in a distributed hashtable (DHT). CFS identifies
 different users' directory trees by the users' cryptographic keys;
-and uses a DHT, to store the mapping from these keys to the
+it uses a DHT to store the mapping from these keys to the
 the current version of a user's tree. 
 The mapping is destructively updated upon receipt of an
 update message that is
 signed with the appropriate key and contains a timestamp
 newer than that of the current version.
-In CFS, version information is stored only
+In CFS, version and other information is stored only
 as long as the publisher regularly requests it to be kept;
 information about past versions is not stored at all.
 
 In *OceanStore* [kubiatowicz00oceanstore]_, 
-an Internet-scale distributed data store based
-on the Tapestry [zhao01tapestry]_ overlay that 
+an Internet-scale distributed data store that,
+based
+on the Tapestry [zhao01tapestry]_ overlay,
 allows users to access their files 
-from different locations, every document has a 
+from different locations, 
+every document has a 
 *primary replica*, a small set of servers that
 maintain the current version of the document.
 To make the connection between a document and a version,