[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 04:46:53

Modified files:
        storm          : article.rst 

Log message:
        resolve one XXX

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.150 manuscripts/storm/article.rst:1.151
--- manuscripts/storm/article.rst:1.150 Fri Feb 14 14:42:10 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 04:46:52 2003
@@ -1000,8 +1000,11 @@
 store the current version as well as the differences,
 enabling them to retrieve the current version quickly and compute
 recent versions by applying the differences 'backwards,'
-starting from the current version. This technique would also be
-made harder by the simplistic scheme above because XXX.
+starting from the current version. If this technique were applied
+in the simplistic scheme above, there would be no guarantee
+that the resulting version would really be the version referred to:
+The cryptographic hashes only guarantee this when all of the
+differences are processed.
 
 The root of these difficulties is that we refer to a version
 by the hash of a data record referencing the previous version,
@@ -1009,7 +1012,7 @@
 before that, and so on. 
 
 To solve this problem, in our current
-design we refer to a version by the hash of that version--
+design we refer to a version simply by the hash of that version--
 that is, the hash of a block containing that version.
 However, we do not necessarily store this block,
 even though we refer to it. Instead, we may create a *diff block*,