[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 12:36:07

Modified files:
        storm          : article.rst 

Log message:
        twid

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.184 manuscripts/storm/article.rst:1.185
--- manuscripts/storm/article.rst:1.184 Sat Feb 15 12:27:55 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 12:36:06 2003
@@ -1078,25 +1078,20 @@
 Conclusions
 ===========
 
-We have addressed two important issues raised by data mobility, dangling 
-links and keeping track of alternative versions. Moreover, we have presented 
-the Storm design, which makes use of recent advances in peer-to-peer 
technology 
-to resolve these issues.  In Storm, all data is stored as immutable blocks and
-each block has globally unique identifier. Application-specific indices can be 
kept
-of these blocks. On top of indexed blocks, we have implemented efficient 
versioned 
+We have introduced the Storm design to address two important issues 
+raised by data mobility, dangling links and keeping track 
+of alternative versions. In Storm, all data is stored as immutable blocks
+identified a SHA-1 hash. Application-specific indices of these blocks can be 
kept.
+On top of indexed blocks, we have implemented efficient versioned 
 storage of mutable resources as well as Xanalogical storage.
 
-Storm is not only limited to network publishing;
+Storm is not limited to network publishing;
 it can be also used for private document repository. Our current 
implementation 
 does not support peer-to-peer distribution yet, but the Gzz project has used 
it 
 for local storage and server-based collaboration for one and a half years.
-
 Currently, we are working on completing our GISP-based peer-to-peer
-implementation of Storm. Once this is done, we intend to explore
-alternative DHT implementations as well. We will also evaluate
-using Merkle hash trees [XXXref] to identify blocks; this would
-allow us to download parts of a block from multiple sources
-simultaneously (as in e.g. [XXX ref Overnet]).
+implementation of Storm. In the future, we intend to explore
+other DHT implementations, too.
 
 No work on integrating Storm with current programs (in the spirit of Open
 Hypermedia) has been done so far. It is not clear how far this is possible
@@ -1108,8 +1103,8 @@
 
 One possibility is to take an existing system
 (with features outside the focus of Gzz)
-that implements strict versioning, and to modify it to use Storm for storage. 
-A candidate is the object-oriented (web) publishing environment Zope [ref 
zope.org/com, book,
+which implements strict versioning, and to modify it to use Storm for storage. 
+A candidate is the object-oriented Web publishing environment Zope [ref 
zope.org/com, book,
 article?], which is Free Software and stores everything by default as diffs to
 a (flat file) database. Another way is studying the applicability of the 
 open hypermedia protocol (OHP) [reich-davis99-ohp].