[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/01 20:51:41

Modified files:
        pointers       : article.rst 

Log message:
        explain freenet better

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.63 
manuscripts/pointers/article.rst:1.64
--- manuscripts/pointers/article.rst:1.63       Sat Nov  1 20:47:55 2003
+++ manuscripts/pointers/article.rst    Sat Nov  1 20:51:41 2003
@@ -113,16 +113,16 @@
 Freenet has a rather peculiar combination 
 of two workarounds [XXXref Freenet FAQ]:
 
-In date-based updating, the key for the current version
+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, versions ``n`` and ``n+1``
-have different URIs, but version ``n`` links to version ``n+1``
-using an ``<img>`` link; the image will not show until
-version ``n+1`` is actually inserted into the system, so
-if the image does show up, the user knows that they can click
+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.
 
 Finally, a simplistic approach to P2P versioning