gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Wed, 05 Feb 2003 17:05:05 -0500

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

Modified files:
        storm          : article.rst 

Log message:
        Move back, shorten

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.90 manuscripts/storm/article.rst:1.91
--- manuscripts/storm/article.rst:1.90  Wed Feb  5 16:59:47 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 17:05:04 2003
@@ -67,6 +67,22 @@
    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. 
+
+Location-independent identifiers for documents 
+make such a notification unnecessary; a peer-to-peer lookup system 
+can resolve them whereever the documents are moved.
+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 use cases
 
 In this paper, we present Storm (for *storage module*), a design 
@@ -130,12 +146,6 @@
 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, 
@@ -149,13 +159,6 @@
    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 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]