gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/pointers article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/pointers article.rst
Date: Mon, 03 Nov 2003 12:09:24 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/03 12:09:24

Modified files:
        pointers       : article.rst 

Log message:
        s/Oceanstore/OceanStore/

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.94 
manuscripts/pointers/article.rst:1.95
--- manuscripts/pointers/article.rst:1.94       Mon Nov  3 11:59:57 2003
+++ manuscripts/pointers/article.rst    Mon Nov  3 12:09:23 2003
@@ -69,7 +69,7 @@
 is signed with the appropriate key, and contains a timestamp
 newer than that of the current version.
 
-In *Oceanstore* [kubiatowicz00oceanstore]_, every document has a
+In *OceanStore* [kubiatowicz00oceanstore]_, every document has a
 *primary replica*, a small set of servers that
 maintain the current version of the document.
 To make the connection between document and version,
@@ -81,7 +81,7 @@
 are believed to be able to cope with looser consistency
 semantics; the NFS client for CFS only requests
 new heartbeats less than 30 seconds old.
-Oceanstore is unique among the versioned P2P systems
+OceanStore is unique among the versioned P2P systems
 in that it implements non-destructive updates,
 allowing previous versions of documents to be accessed
 (by using their old heartbeats).
@@ -90,7 +90,7 @@
 update mechanism where the network would remember
 the current version of a document, and update this information
 when receiving a message signed by the appropriate key,
-rather like in Oceanstore. However, in practice,
+rather like in OceanStore. However, in practice,
 Freenet has a rather peculiar combination 
 of two workarounds [freenetfaq]_.
 In date-based updating, the URI for the current version
@@ -170,7 +170,7 @@
    network transparency and location independence (ref ourselves).
 
 The main contribution of our paper are *pointer records*,
-a versioning mechanism which is similar to Oceanstore's heartbeats,
+a versioning mechanism which is similar to OceanStore's heartbeats,
 but makes the clients download and store the pointer records
 along with the corresponding version of a document.
 If a client saves a version of a document locally, it
@@ -204,7 +204,7 @@
 Similar to searching different P2P networks in order
 to resolve a SHA-1 hash, you can search different networks
 to find pointer records for a document. A document
-could be originally edited in Oceanstore, then published
+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.
 
@@ -248,7 +248,7 @@
 owned by the same entity.
 
 To associate pointers with versions, our system uses *pointer records*
-small files that, similar to Oceanstore's heartbeats,
+small files that, similar to OceanStore's heartbeats,
 are signed by the pointer's owner, and
 contain at least the following information:
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]