[Gzz-commits] manuscripts/storm article.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Hermanni Hyytiälä <address@hidden>      03/02/12 07:35:18

Modified files:
        storm          : article.rst 

Log message:
        Misc updates and fixes

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.131 manuscripts/storm/article.rst:1.132
--- manuscripts/storm/article.rst:1.131 Wed Feb 12 06:31:03 2003
+++ manuscripts/storm/article.rst       Wed Feb 12 07:35:18 2003
@@ -6,11 +6,10 @@
 ========
 
 We define data mobility as a collective term for the
-movement of documents between computers, locations on one computer and
+movement of documents between computers, different locations on one computer 
and
 movement of content between documents.
 We identify dangling links, tracking identity and alternative versions as
-obstacles for the free movement of data,
-and review
+obstacles for the free movement of data, and review
 motivations and potential solutions in existing hypermedia research.
 We discuss some specific use scenarios, related to ad hoc networks,
 unreliable network connections and mobile computing
@@ -20,9 +19,8 @@
 
 We present Storm (STORage Module) design as one possible solution
 to the problems in the above scenarios.
-Storm uses
-location-independent globally unique identifiers, immutable block storage
-and peer-to-peer networking to .... 
+Storm uses location-independent, globally unique identifiers, 
+immutable block storage and peer-to-peer networking to .... 
 
 Our current, partial implementation ...
 
@@ -35,7 +33,7 @@
 
 Keywords: hypermedia, versioned hypermedia, dangling links, xanalogical 
storage, P2P, 
 peer-to-peer, location-independent identifiers, location-independent routing, 
-distributed hashtables
+distributed hashtables, DHT
 
 
 1. Introduction
@@ -104,9 +102,9 @@
 on the public Internet. 
 
 Location-independent identifiers for documents 
-make such a system unnecessary; a peer-to-peer lookup system 
+make such a system unnecessary; a structured peer-to-peer lookup system 
 can find documents wherever they are moved.
-Such a system also works for data not publicized on the Internet.
+This kind of 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.
@@ -128,7 +126,7 @@
 to work on the version at hand and then either merge it with others 
 or fork to a different branch.
 
-In this paper, we present Storm (for *storage module*), a design 
+In this paper, we present Storm (for *STOrage Module*), a design 
 dealing with versioning and dangling links. Storm is a library
 for storing and retrieving data as *blocks*, immutable
 byte sequences identified by cryptographic content hashes
@@ -140,16 +138,13 @@
 
 The main contribution of this paper is the Storm design, 
 a hypermedia system built to use the emerging 
-peer-to-peer search technologies to enhance data mobility. 
+peer-to-peer data lookup technologies to enhance data mobility. 
 Additionally, we hope to 
 provide an input to the ongoing discussion about peer-to-peer
 hypermedia systems [ref ht01, ht02].
-
 Currently, Storm is partially implemented as a part of the Gzz 
 project [ref], which uses Storm exclusively for all disk storage.
-Gzz is an implementation of Ted Nelson's zzstructure [ref],
-providing a platform for hypermedia-aware applications.
-The peer-to-peer functionality is in a very early stage and not 
+Storm's peer-to-peer functionality is in a very early stage and not 
 usable yet.
 
 This paper is structured as follows. In the next section, we describe 
@@ -388,6 +383,7 @@
 
 .. Should we discuss applications of p2p systems (CFS, OceanStore, Squirrel, 
...)
    here? If so, which ones?
+   [CFS/PAST(DHT, GUID, block vs. files), perhaps Freenet too (GUID) ? 
-Hermanni]
 
 .. thesis-benja: remove paragraph below
 
@@ -973,6 +969,8 @@
 due Feb 9th, so I want all possible improvements on it
 to go there, too ;-) [and I'm of course allowed to solicite feedback,
 but not allowed to use stuff written by someone else...]]
+[Hm, should we move/remove 'Additionally, many versioning'
+paragraph into related work ? -Hermanni]
 
 The pointer system suggests that for each version of a document,
 we store an independent block containing this version. This
@@ -1259,7 +1257,7 @@
 
    One possibility: Use IBP for limited-time publishing, referring to
    the location through the DHT? This might be related to p2p publishing.
-
+   
 
 8. Conclusions
 ==============
@@ -1286,11 +1284,11 @@
 we believe that it is valuable as an exercise in what is possible
 if we can break backwards compatibility with the state of the art.
 
-At the very least, we hope to provide a case study in
+At the end, we hope that we have provided a case study in
 what's possible in a system that does not use
 location-dependent identifiers at all. We hope to raise awareness
 for the prospects of location-independent systems based
-on structured overlay networks like DHTs.
+on structured overlay networks such as DHTs.
 
 
 9. Acknowledgements