[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 02:56:46

Modified files:
        pointers       : article.rst 

Log message:
        Reorder other systems: from lightest to heaviest

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.179 
manuscripts/pointers/article.rst:1.180
--- manuscripts/pointers/article.rst:1.179      Sun Nov  9 14:11:59 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 02:56:45 2003
@@ -247,6 +247,41 @@
 In this section, we shall briefly discuss the existing approaches
 to document updates in P2P systems.
 
+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* 
+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.
+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.
+
+*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,
+Freenet has a rather peculiar combination 
+of two workarounds [freenetfaq]_.
+In date-based updating, the URI for the current version
+is formed by concatenating a document's id with the current date;
+this requires publishers to insert versions of their document
+every day, otherwise they will not be accessible.
+In edition-based updating, a version's URI is the document's id
+concatenated with a version number. Version ``n`` then links to 
+version ``n+1`` using an ``<img>`` link. The image will not show until
+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.
+
 *CFS* [dabek01widearea]_
 is a file system based on Chord [stoica01chord]_, storing
 data in a distributed hashtable (DHT). CFS identifies
@@ -289,41 +324,6 @@
    are believed to be able to cope with looser consistency
    semantics; for example, the NFS client for OceanStore only requests
    new heartbeats less than 30 seconds old.
-
-*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,
-Freenet has a rather peculiar combination 
-of two workarounds [freenetfaq]_.
-In date-based updating, the URI for the current version
-is formed by concatenating a document's id with the current date;
-this requires publishers to insert versions of their document
-every day, otherwise they will not be accessible.
-In edition-based updating, a version's URI is the document's id
-concatenated with a version number. Version ``n`` then links to 
-version ``n+1`` using an ``<img>`` link. The image will not show until
-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
-of a document, such 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.
-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.
 
 
 Pointer records