[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

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

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.179&tr2=1.180&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.179 manuscripts/storm/article.rst:1.180
--- manuscripts/storm/article.rst:1.179 Sat Feb 15 12:15:20 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 12:17:15 2003
@@ -1092,20 +1092,15 @@
 allow us to download parts of a block from multiple sources
 simultaneously (as in e.g. [XXX ref Overnet]).
 
-Storm has proven to be a solid basis for Gzz, but
-no work has been done to integrate it with existing systems, yet.
-This makes Storm a rather monolithic approach at present.
-However, even if Storm-- or especially Xanalogical storage--
-should be hard to integrate with existing systems,
-we believe that it is valuable as an exercise in what is possible
-if we can break backwards compatibility with the state of the art.
-
 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
 without changing applications substantially, if advantage of our
 implementation of Xanalogical storage is to be taken. Vitali 
[vitali99versioning]_
 notes that Xanalogical storage necessiates strong discipline in version 
tracking,
-which current systems lack. One possibility is to take an existing system
+which current systems lack. 
+This makes Storm a rather monolithic approach at present.
+
+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,
@@ -1117,7 +1112,7 @@
 as well -- for example the conventions for listing, moving and deleting
 blocks.
 
-At the end, we hope that we have provided a case study in
+We have provided a case study in
 what's possible in a system that does not use
 location-dependent identifiers at all. We hope to raise awareness
 for the prospects of location-independent systems based