[Gzz-commits] manuscripts/storm TODO article.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Hermanni Hyytiälä <address@hidden>      03/02/13 08:48:08

Modified files:
        storm          : TODO article.rst 

Log message:
        Conclusion improvements

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/TODO.diff?tr1=1.3&tr2=1.4&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.141&tr2=1.142&r1=text&r2=text

Patches:
Index: manuscripts/storm/TODO
diff -u manuscripts/storm/TODO:1.3 manuscripts/storm/TODO:1.4
--- manuscripts/storm/TODO:1.3  Wed Feb 12 10:54:45 2003
+++ manuscripts/storm/TODO      Thu Feb 13 08:48:08 2003
@@ -4,7 +4,7 @@
 - layout: uml into figures at least (I kludged this for thesis) [benja]
 - image of xupdf, hopefully discussion [benja, 
   dep screenshot from ppl involved with xupdf]
-- summarize the important open issues [benja]
+- summarize the important open issues and outline most important (near) future 
plans [benja]
 - either rework the use cases back to original idea (more 'personal')
   or let them be in current form but finish them (make complete&correct) 
[antont]
 - discuss current status [benja]
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.141 manuscripts/storm/article.rst:1.142
--- manuscripts/storm/article.rst:1.141 Thu Feb 13 08:30:37 2003
+++ manuscripts/storm/article.rst       Thu Feb 13 08:48:08 2003
@@ -40,7 +40,7 @@
 ===============
 
 The Web and many other hypermedia systems assume that identifiers
-either have to include location information (as in URLs, which break 
+either have to include location information (as in regular URLs, which break 
 when documents are moved), or can only be resolved locally (as in
 link services that can only find links stored on a select set
 of link servers [ref Microcosm, DLS, ...]). Berners-Lee [ref NameMyth - that
@@ -52,18 +52,18 @@
 [ref chord, can, tapestry, pastry, kademlia, symphony, viceroy,
 skip graph, swan, kelips] allow location-independent identifiers
 to be resolved on a global scale. 
-Thus, it is now feasible to do a global search to find all information
+Thus, it is now possible to perform a global lookup to find all information
 related to a given identifier on any participating peer in the network.
 This, we believe, may be the most important result of peer-to-peer 
 research with regard to hypermedia.
 
-We examine how location-independent identifiers can support *data mobility*.
-In today's computing world, documents move quite freely between 
-computers: they are sent as e-mail attachments, carried around on disks,
-published on the web, moved between desktop and laptop systems,
-downloaded for off-line reading or copied between computers in a LAN. 
-We use 'data mobility' as a collective term for the movement of documents
-between computers (or folders!),
+In this paper, we examine how location-independent identifiers can 
+support *data mobility*. Our motivation has been inspired by today's computing 
+world, in which documents move quite freely between computers: they are sent 
as 
+e-mail attachments, carried around on disks, published on the web, moved 
+between desktop and laptop systems, downloaded for off-line reading or 
+copied between computers in a LAN. We use 'data mobility' as a collective 
+term for the movement of documents between computers (or folders!),
 and movement of content between documents (through copy&paste) [#]_.
 
 .. [#] While the physical mobility of e.g. notebooks may effect
@@ -71,7 +71,7 @@
    data mobility is neither the same as, nor limited to the physical
    movement of devices.
 
-In this paper, we address two issues raised by data mobility:
+We address two issues raised by data mobility:
 Dangling links and keeping track of alternative versions. 
 Resolvable location-independent identifiers
 make these issues much easier to deal with, since data
@@ -1272,19 +1272,18 @@
 8. Conclusions
 ==============
 
-We have presented the Storm design, which makes use of recent advances
-in peer-to-peer technology to support many different forms
-of data mobility. All data is stored in immutable blocks,
-of which application-specific indices can be kept. On top of
-indexed blocks, we implement efficient versioned storage
-of mutable resources as well as Xanalogical storage.
-
-Storm is not limited to network publishing;
-it is intended to be used for private documents stored on
-desktop systems as well. Our current implementation does not support
-peer-to-peer distribution yet, but the Gzz project has used it 
-for local storage and server-based collaboration
-for one and a half years.
+We have addressed two important issues raised by data mobility, dangling 
+links and keeping track of alternative versions. Moreover, we have presented 
+the Storm design, which makes use of recent advances in peer-to-peer 
technology 
+to resolve these issues.  In Storm, all data is stored as immutable blocks and
+each block has globally unique identifier. Application-specific indices can be 
kept
+of these blocks. On top of indexed blocks, we have implemented efficient 
versioned 
+storage of mutable resources as well as Xanalogical storage.
+
+Storm is not only limited to network publishing;
+it can be also used for private document repository. Our current 
implementation 
+does not support peer-to-peer distribution yet, but the Gzz project has used 
it 
+for local storage and server-based collaboration for one and a half years.
 
 Storm has proven to be a solid basis for Gzz, but
 no work has been done to integrate it with existing systems, yet.