[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/06 02:11:51

Modified files:
        pointers       : article.rst 

Log message:
        shorten intro, comment out one paragraph-- now fits on 5 pages again!

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.139 
manuscripts/pointers/article.rst:1.140
--- manuscripts/pointers/article.rst:1.139      Thu Nov  6 02:01:35 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 02:11:51 2003
@@ -208,29 +208,17 @@
 a versioning mechanism which is similar to OceanStore's heartbeats,
 but allows the clients to download and store the pointer records
 along with the corresponding version of a document.
-If a client caches a version of a document locally, it
-stores the pointer record along with it. 
 Instead of having a primary replica, we search
-the P2P network for current pointer records
-related to a document; we pick the one with
-the most current timestamp as the version
-to show to the user by default; old versions 
-remain equally accessible 
-as long as
-anybody keeps a copy.
+the whole P2P network for pointer records
+related to a document.
 
 An additional contribution is the Storm data model,
-an API formalizing the notion of hash-based addressing
-and content-based lookup that can be implemented
-using many different P2P architectures (including
-DHTs and the flooding broadcast search of Gnutella [gnutellaurl]_).
-The Storm data model provides a convenient interface
-to applications such as Web browsers, which then
-need not worry about the P2P network(s) used to
-resolve the identifiers. Pointer records can be implemented
-on top of the Storm model, meaning that they do not
-need to be implemented separately for each time of
-P2P network.
+an API formalizing the notion of searching for data
+by hash and content. The API is used by applications
+such as browsers and implemented for each P2P network
+accessed. Pointer records can be implemented
+on top of the Storm model, rather than separately
+for each P2P network.
 
 ..  Like in OceanStore, old
     versions remain fully accessible (as long as somebody
@@ -243,8 +231,8 @@
 would have the benefits of semantic-free referencing--
 URIs don't have to change because of trademark conflicts
 as in DNS, for example-- but go beyond the proposal
-by Balakrishnan et.al. [balakrishnan03semanticfree]_, 
-for replacing DNS but keeping the centralized architecture of
+by Balakrishnan et.al. [balakrishnan03semanticfree]_
+to replace DNS but keep the centralized architecture of
 one Web server (or a single set of servers) maintained
 by the publisher of a document.
 
@@ -324,7 +312,7 @@
 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 can search different networks
+to resolve a SHA-1 hash, you could search different networks
 to find pointer records for a document. A document
 could be originally edited in OceanStore, then published
 in Gnutella or a DHT-based system, using an anonymized system
@@ -395,12 +383,14 @@
     The server would publish the resulting mappings
     from words to block ids on the P2P network.
 
-An index can also return additional information
-to be placed in the hashtable along with the
-block id. In the example, this could be the complete
-metadata of the song, so that a client does not need
-to download the complete audio file before being able
-to show its artist, title etc. to its user.
+.. XXX kept out because of space constraints:
+
+   An index can also return additional information
+   to be placed in the hashtable along with the
+   block id. In the example, this could be the complete
+   metadata of the song, so that a client does not need
+   to download the complete audio file before being able
+   to show its artist, title etc. to its user.
 
 The pointer functionality is trivial to implement
 *on top of* this basic model. A pointer record