[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/05 16:59:47

Modified files:
        storm          : article.rst 

Log message:
        move stuff from introduction

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.89 manuscripts/storm/article.rst:1.90
--- manuscripts/storm/article.rst:1.89  Wed Feb  5 16:43:32 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 16:59:47 2003
@@ -60,41 +60,14 @@
 make these issues much easier to deal with, since data
 can be recognized whereever it is moved. 
 
-{{The design also allows for
-automatic balancing of the load, which occurs in location-dependent
-situations with popular items. [benja says: This is not related
-to the central point as expressed in the title; therefore, I believe
-it should be given as a benefit of the system somewhere later
-in the paper (like many others) but not put here...]}}
+.. The design also allows for
+   automatic balancing of the load, which occurs in location-dependent
+   situations with popular items. [benja says: This is not related
+   to the central point as expressed in the title; therefore, I believe
+   it should be given as a benefit of the system somewhere later
+   in the paper (like many others) but not put here...]
 
-Advanced hypermedia systems such as Microcosm and Hyper-G
-address dangling links through a notification system:
-When a document is moved, servers storing links to it are notified.
-Hyper-G uses an efficient protocol for delivering such notifications
-on the public Internet. 
-
-The use of location-independent identifiers
-for documents, resolved through a peer-to-peer lookup system, 
-makes such a notification unnecessary; when a document is moved, 
-but retains its identifier, it can be found by the same mechanism as
-before the move. It is possible to retrieve the document
-from any system storing a copy; this means that documents may be
-accessible even after the original publisher has taken them off-line [#]_.
-
-.. [#] Intentionally or unintentionally. We believe that it is 
-   a good thing if published documents remain available even when
-   the original publisher wants to retract them; however, discussion
-   of the ethical implications of this is outside the scope of this paper.
-   (But see [XXX search for refs! ;-)])
-
-Such a system also works for data not publicized on the Internet.
-For example, if one email has a document attached to it, and another email
-links to this document, an index of locally stored documents
-by permanent identifier allows the system to follow the link.
-This would be extremely difficult to realize through a
-notification mechanism like Microcosm's and Hyper-G's.
-
-XXX say something about versioning
+XXX use cases
 
 In this paper, we present Storm (for *storage module*), a design 
 dealing with these issues. Storm is a library
@@ -117,12 +90,13 @@
 .. [General figure of Storm, i.e. application layer, storm layer, 
    netowork layer ? -Hermanni]
  
-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 [ref] notes that Xanalogical storage necessiates
-strong discipline in version tracking, which current systems lack.)
+.. [Move somewhere else -b]:
+   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 [ref] notes that Xanalogical storage necessiates
+   strong discipline in version tracking, which current systems lack.)
 
 .. Investigating the degrees of interoperability with Open Hypermedia
    (/Structural Computing?) and (more primitive?) other (Web) XXX is a possible
@@ -155,6 +129,33 @@
 In advanced hypermedia systems such as Microcosm[] and Hyper-G[],
 several approaches has been proposed to deal with the dangling/other link
 management problems. 
+
+Advanced hypermedia systems such as Microcosm and Hyper-G
+address dangling links through a notification system:
+When a document is moved, servers storing links to it are notified.
+Hyper-G uses an efficient protocol for delivering such notifications
+on the public Internet. 
+
+The use of location-independent identifiers
+for documents, resolved through a peer-to-peer lookup system, 
+makes such a notification unnecessary; when a document is moved, 
+but retains its identifier, it can be found by the same mechanism as
+before the move. It is possible to retrieve the document
+from any system storing a copy; this means that documents may be
+accessible even after the original publisher has taken them off-line [#]_.
+
+.. [#] Intentionally or unintentionally. We believe that it is 
+   a good thing if published documents remain available even when
+   the original publisher wants to retract them; however, discussion
+   of the ethical implications of this is outside the scope of this paper.
+   (But see [XXX search for refs! ;-)])
+
+Such a system also works for data not publicized on the Internet.
+For example, if one email has a document attached to it, and another email
+links to this document, an index of locally stored documents
+by permanent identifier allows the system to follow the link.
+This would be extremely difficult to realize through a
+notification mechanism like Microcosm's and Hyper-G's.
 
 Microcosm addressed the linking problems of large archives 
 by separating the links from the documents and storing them on dedicated