/[gzz]/manuscripts/pointers/article.rst
ViewVC logotype

Diff of /manuscripts/pointers/article.rst

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.215 by benja, Mon Nov 10 11:54:30 2003 UTC revision 1.216 by benja, Mon Nov 10 12:01:35 2003 UTC
# Line 369  As the pointer id, we use the hash of th Line 369  As the pointer id, we use the hash of th
369  a file including identification information for the pointer's owner,  a file including identification information for the pointer's owner,
370  the entity that has change control over the document.  the entity that has change control over the document.
371  This can be the owner's public key, or information about the CA  This can be the owner's public key, or information about the CA
372    (Certificate Authority)
373  from which the owner's current public key can be obtained.  from which the owner's current public key can be obtained.
374  The charter also includes information  The charter also includes information,
375    e.g. a semantic-free random bitstring,
376  to distinguish the pointer from all other documents  to distinguish the pointer from all other documents
377  owned by the same entity, for example  owned by the same entity.
378  a semantic-free random  
 bitstring.  
379    
380  To associate pointers with versions, our system uses *pointer records*:  To associate pointers with versions, our system uses *pointer records*:
381  small files that, similar to OceanStore's heartbeats,  small files that, similar to OceanStore's heartbeats,
# Line 392  The list of available records can be obt Line 393  The list of available records can be obt
393  peer-to-peer network; this could be a DHT, a flooding broadcasting  peer-to-peer network; this could be a DHT, a flooding broadcasting
394  network like Gnutella [gnutellaurl]_, or any other P2P architecture.  network like Gnutella [gnutellaurl]_, or any other P2P architecture.
395    
396  Contrary to other systems,  Unlike in other systems,
397  pointer records are treated as *first-class citizens*;  pointer records are treated as *first-class citizens*;
398  pointer records  they are normal data files
 are simply normal data files  
399  and may reside on (and be downloaded from) any host.  and may reside on (and be downloaded from) any host.
400  For example, a filesharing system could, for every versioned  For example, a filesharing system could, for every versioned
401  file ``f``, store two companion files ``f.version``  file ``f``, store two companion files ``f.version``
# Line 419  Because they require no centralized vers Line 419  Because they require no centralized vers
419  pointer records may be able to unify the namespaces  pointer records may be able to unify the namespaces
420  of different P2P systems in a similar way to hash-based identifiers.  of different P2P systems in a similar way to hash-based identifiers.
421  Similar to searching different P2P networks in order  Similar to searching different P2P networks in order
422  to resolve a SHA-1 hash, you could search different networks  to resolve an SHA-1 hash, you could search different networks
423  to find pointer records for a document. A document  to find pointer records for a particular document. A document
424  could be originally edited in OceanStore, then published  could be originally edited in OceanStore, then published
425  in Gnutella or a DHT-based system, using an anonymized system  in Gnutella or a DHT-based system, using an anonymized system
426  like Achord [hazel02achord]_ if it contains controversial content.  like Achord [hazel02achord]_ if it contains controversial content.

Legend:
Removed from v.1.215  
changed lines
  Added in v.1.216

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26