[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/10 07:01:35

Modified files:
        pointers       : article.rst 

Log message:
        twid pointer records section

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.215 
manuscripts/pointers/article.rst:1.216
--- manuscripts/pointers/article.rst:1.215      Mon Nov 10 06:54:30 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 07:01:35 2003
@@ -369,12 +369,13 @@
 a file including identification information for the pointer's owner,
 the entity that has change control over the document.
 This can be the owner's public key, or information about the CA
+(Certificate Authority)
 from which the owner's current public key can be obtained.
-The charter also includes information
+The charter also includes information,
+e.g. a semantic-free random bitstring,
 to distinguish the pointer from all other documents
-owned by the same entity, for example
-a semantic-free random
-bitstring.
+owned by the same entity.
+
 
 To associate pointers with versions, our system uses *pointer records*:
 small files that, similar to OceanStore's heartbeats,
@@ -392,10 +393,9 @@
 peer-to-peer network; this could be a DHT, a flooding broadcasting
 network like Gnutella [gnutellaurl]_, or any other P2P architecture.
 
-Contrary to other systems, 
+Unlike in other systems, 
 pointer records are treated as *first-class citizens*;
-pointer records
-are simply normal data files 
+they are normal data files 
 and may reside on (and be downloaded from) any host.
 For example, a filesharing system could, for every versioned 
 file ``f``, store two companion files ``f.version`` 
@@ -419,8 +419,8 @@
 pointer records may be able to unify the namespaces
 of different P2P systems in a similar way to hash-based identifiers.
 Similar to searching different P2P networks in order
-to resolve a SHA-1 hash, you could search different networks
-to find pointer records for a document. A document
+to resolve an SHA-1 hash, you could search different networks
+to find pointer records for a particular document. A document
 could be originally edited in OceanStore, then published
 in Gnutella or a DHT-based system, using an anonymized system
 like Achord [hazel02achord]_ if it contains controversial content.