[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/12 06:24:40

Modified files:
        storm          : article.rst 

Log message:
        started to rework the use case review to fit how Benja 'melted' them in 
the intro

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.129 manuscripts/storm/article.rst:1.130
--- manuscripts/storm/article.rst:1.129 Tue Feb 11 14:54:00 2003
+++ manuscripts/storm/article.rst       Wed Feb 12 06:24:40 2003
@@ -1129,6 +1129,22 @@
 agreed with benja on irc that we might try this approach - hinting about the
 use cases early on and taking a detailed look later, in light of the design.)
 
+evaluation
+----------
+
+To evaluate the design, the issues raised by data mobility are revisited in
+the following. For the two issues addressed, *danglink links* and *tracking
+alternative versions*, each individual (use) case that was identified in the
+introduction is used here to illustrate Storm.
+
+*Dangling links*. When documents are moved between servers, when using Storm
+the links to them are not affected as the identifiers are
+location-independent. In a peer-to-peer implementation, the lookup with the
+id returns a location where the data is currently available. If the
+publisher removes the document permanently, but it is archived elsewhere,
+the archives act as peers similarly. When there is no network connection
+available, but a local copy instead, the lookup points to that.
+
 1. live meeting:
 Documents have been assigned block-ids (and urns?) at creation.
 Pools that are shared / set visible for the other user show over the