[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/06 09:52:34

Modified files:
        pointers       : article.rst 

Log message:
        edit

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.159 
manuscripts/pointers/article.rst:1.160
--- manuscripts/pointers/article.rst:1.159      Thu Nov  6 09:48:09 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 09:52:33 2003
@@ -129,6 +129,9 @@
 in the DHT will update a mapping if the update message
 is signed with the appropriate key, and contains a timestamp
 newer than that of the current version.
+In CFS, version information is stored in the DHT, and only
+as long as the publisher regularly requests it to be kept;
+information about past versions isn't stored at all.
 
 In *OceanStore* [kubiatowicz00oceanstore]_, 
 an Internet-scale distributed data store that 
@@ -146,6 +149,11 @@
 in that it implements non-destructive updates,
 allowing previous versions of documents to be accessed
 (by using their old heartbeats).
+In OceanStore, requesting a document's current version
+depends on querying its primary replica; when the primary
+replica ceases to function, the current version cannot be
+determined any longer (for some applications, this only happens
+30 seconds after the primary replica disappears).
 
 .. [#consistencytime] Many applications
    are believed to be able to cope with looser consistency
@@ -170,6 +178,9 @@
 version ``n+1`` is actually inserted into the system; thus,
 when the image does show up, the user knows that they should click
 on it to get to a newer version of the document.
+In Freenet, files only stay online as long as they are
+requested regularly; keeping a copy on your harddisk
+does not keep a page alive.
 
 Finally, a simplistic approach to P2P versioning
 is to have a centralized server keep track of the current version
@@ -181,21 +192,12 @@
 However, there is still a single point of failure, and
 links still break when pages move to a different directory
 or Web server.
-
-In a filesharing system, a file remains accessible
-as long as there is a copy on any of the participating hosts.
-None of the above versioning systems have this property.
-In CFS, version information is stored in the DHT, and only
-as long as the publisher regularly requests it to be kept.
-In OceanStore, requesting a document's current version
-depends on querying its primary replica; when the primary
-replica ceases to function, the current version cannot be
-determined any longer (for some applications, this only happens
-30 seconds after the primary replica disappears).
-In Freenet, files only
-remain on-line as long as they are requested regularly in any case.
 In the Content-Addressable Web proposal, the situation
-is the same as on the current Web.
+regarding versioning is the same as on the current Web.
+
+In conclusion, a filesharing system, a file remains accessible
+as long as there is a copy on any of the participating hosts;
+none of the above versioning systems have this property.
 
 Thus, in these systems, when the original publisher loses interest
 and stops publishing a page, it disappears, even if