[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/10 04:25:54

Modified files:
        pointers       : article.rst 

Log message:
        tighten section about Storm model

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

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.190 
manuscripts/pointers/article.rst:1.191
--- manuscripts/pointers/article.rst:1.190      Mon Nov 10 04:19:57 2003
+++ manuscripts/pointers/article.rst    Mon Nov 10 04:25:53 2003
@@ -452,8 +452,10 @@
     generalization of reverse indexing
 
 In this section, we introduce the Storm [#]_ data model, 
-an API providing simple but powerful abstraction over both local storage
-and several types of P2P network. The intent
+an API for storing and retrieving information using
+hash-based addressing. Storm provides a simple but powerful
+abstraction over both local storage and several types
+of P2P networks. The intent
 of this API is to decouple the application and network layers
 so that both can evolve independently.
 
@@ -472,7 +474,7 @@
 .. XXX NOTE: if we move any sections around, update
    the above section number!
 
-The model is comprised of the following components:
+The model is comprised of two components:
 
 Blocks, identified by hash
     All data is stored in *blocks*, which are file-like,
@@ -481,20 +483,6 @@
     plus a MIME content type. (The MIME type is the minimal amount
     of metadata necessary in addition to the content 
     for showing a block in a Web browser.)
-
-Pools
-    A *pool* is a collection of blocks. The data published
-    by a particular P2P Web server, the data downloaded
-    by a client, the data in a client's cache, and all 
-    data available on the whole P2P Web can each be seen as a pool.
-    A pool provides the functionality to
-    fetch a block by its global id; local (cache- or filesystem-like)
-    pools also allow
-    blocks to be added, deleted and iterated over.
-    A user would generally have at least three local pools:
-    blocks I've created; blocks I've created and publish on the P2P Web;
-    blocks I've downloaded and cached from elsewhere that may also
-    be shared on the P2P Web.
 
 Reverse indices
     Reverse indices are application-specific plug-ins