[Gzz-commits] manuscripts/storm article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/02/15 14:32:29

Modified files:
        storm          : article.rst 

Log message:
        twid

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.211 manuscripts/storm/article.rst:1.212
--- manuscripts/storm/article.rst:1.211 Sat Feb 15 14:30:38 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 14:32:29 2003
@@ -677,8 +677,7 @@
 create a block with all characters entered in this session (the content type
 being ``text/plain``). To designate a span of characters
 from that session, we use the block's id, the offset of the first
-character, and the number of characters in the span.
-This technique was first introduced in [lukka02guids]_.
+character, and the number of characters in the span [lukka02guids]_.
 
 In Xanadu, characters are stored to append-only *scrolls*
 when they are typed [ref?]. Because of this, in Storm, we call the 
@@ -691,7 +690,8 @@
 .. [#] It is unclear whether this approach is efficient for text
    in the Storm framework; in the future, we may try storing
    the characters in the documents themselves, along with their
-   permanent identifiers. For images or video, on the other hand,
+   permanent identifiers; however, this makes spoofing
+   possible. For images or video, on the other hand,
    it is clearly beneficial if content appearing in different
    documents-- or different versions of a document-- is only
    stored once, in a block only referred to wherever
@@ -713,7 +713,7 @@
 =====================================
 
 Finding links and transclusions in
-Xanalogical storage is only one example of *reverse indexing*
+Xanalogical storage is an example of *reverse indexing*
 of Storm blocks: finding a block based on its contents.
 (For other examples, see section 6, below.)
 Storm provides a general API for indexing blocks in
@@ -789,11 +789,11 @@
 Versioning
 ==========
 
-We implement mutable documents on top of block storage
-using a combination of two mechanisms.
-Firstly, a *pointer* is an updatable reference to a block.
-Secondly, similar to version control systems like CVS,
-we do not store each version, but only the differences between versions.
+Mutable documents can be implemented on top of block storage
+using a combination of two mechanisms, *pointers* and *diffs*.
+A *pointer* is an updatable reference to a block,
+and a diff is a set of differences between versions,
+similar to what is stored e.g. by version control systems such as CVS.
 
 
 Pointers: implementing mutable resources