[Gzz-commits] manuscripts/pointers article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/10/29 07:32:20

Modified files:
        pointers       : article.rst 

Log message:
        Start pointer records

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.33 
manuscripts/pointers/article.rst:1.34
--- manuscripts/pointers/article.rst:1.33       Wed Oct 29 07:08:06 2003
+++ manuscripts/pointers/article.rst    Wed Oct 29 07:32:19 2003
@@ -360,26 +360,31 @@
 Pointer records
 ===============
 
-- In this section, we discuss a particular way
-  of implementing pointers (this is our main contribution)
-- The association between a pointer and a version is formed
-  by a special kind of block, the *pointer record*
-- A pointer record is like a heartbeat in OceanStore;
-  difference: we do it within the basic framework of sets of blocks.
-
-  - Signatures
-  - Timestamp for ordering the records/versions (note on problems
-    this entails-- if a computer's clock is set into future etc)
-
-- Implementable in other systems, too [XXX is this still a point
-  given that OceanStorm does something similar?]
-- Carries over the four benefits from hash-based addressing:
-
-  - Version references movable between servers
-  - Past versions accessible as long as anyone keeps a copy
-  - Load balancing (download the pointer record from whoever has it)
-  - Can use one addressing scheme for *updateable* information,
-    searching different networks for versions
+This Section gives our main contribution: a way
+to implement a persistent, distributed versioning
+system relying only on the abstraction presented
+in the previous section.
+
+..  - In this section, we discuss a particular way
+      of implementing pointers (this is our main contribution)
+    - The association between a pointer and a version is formed
+      by a special kind of block, the *pointer record*
+    - A pointer record is like a heartbeat in OceanStore;
+      difference: we do it within the basic framework of sets of blocks.
+
+      - Signatures
+      - Timestamp for ordering the records/versions (note on problems
+       this entails-- if a computer's clock is set into future etc)
+
+    - Implementable in other systems, too [XXX is this still a point
+      given that OceanStorm does something similar?]
+    - Carries over the four benefits from hash-based addressing:
+
+      - Version references movable between servers
+      - Past versions accessible as long as anyone keeps a copy
+      - Load balancing (download the pointer record from whoever has it)
+      - Can use one addressing scheme for *updateable* information,
+       searching different networks for versions
 
 
 Diffs
@@ -445,3 +450,4 @@
    are ideally to an immutable version, and in which references
    are generally not circular, making this domain map neatly
    to the properties of hash-based referencing.
+   XXX Except for "in press", "unpublished manuscripts", ...