[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

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

Modified files:
        storm          : article.rst 

Log message:
        More intro

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.86 manuscripts/storm/article.rst:1.87
--- manuscripts/storm/article.rst:1.86  Wed Feb  5 15:27:59 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 16:13:09 2003
@@ -58,18 +58,52 @@
 Dangling links and keeping track of alternative versions. 
 Resolvable location independent identifiers
 make these issues much easier to deal with, since data
-can be recognized whereever it is moved. {{The design also allows for
+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.}}
+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
 
 In this paper, we present Storm (for *storage module*), a design 
 dealing with these issues. Storm is a library
-for storing and retrieving data in immutable
+for storing and retrieving data as immutable
 byte sequences identified by cryptographic content hashes
 [ref ht'02 paper], unifying the namespaces of
 private data and documents published on the Internet by
 using the same identifiers for both. Storm provides services
-for storing versioned data and Xanalogical storage [ref].
+for versioned data and Xanalogical storage [ref].
 The Storm design, a hypermedia system built to make use
 of the emerging peer-to-peer search technologies,
 is the main contribution of this paper.