[Gzz-commits] manuscripts/storm short-paper.rst

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Hermanni Hyytiälä <address@hidden>      03/05/30 03:56:23

Modified files:
        storm          : short-paper.rst 

Log message:
        Twids, additions, suggestions

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/short-paper.rst.diff?tr1=1.15&tr2=1.16&r1=text&r2=text

Patches:
Index: manuscripts/storm/short-paper.rst
diff -u manuscripts/storm/short-paper.rst:1.15 
manuscripts/storm/short-paper.rst:1.16
--- manuscripts/storm/short-paper.rst:1.15      Thu May 29 21:55:56 2003
+++ manuscripts/storm/short-paper.rst   Fri May 30 03:56:23 2003
@@ -12,15 +12,26 @@
 .. We argue that while non-breaking links would be a convenience 
    on the Web, they are a necessity for making Web-like hyperlinks
    useful on the local desktop.
-
+   
+.. My suggestion for starting abstract:
+   Linking personal documents like we link Web pages is inconvenient 
+   enough that users rarely ever do it.
+   We argue that while non-breaking links would be a convenience 
+   on the Web, they are a necessity for making Web-like hyperlinks
+   useful on the local desktop. (move "A major reason..." to intro ?) [HH] 
+   
 We propose Storm, a storage system for use both on the
 desktop and the public network. Storm assigns each document
 a permanent URI when it is created. Using peer-to-peer
-technology, we can find documents even though our URIs
+technology, we can locate documents even though our URIs
 do not include location information.
 Thus, links continue to work unchanged when documents are emailed
 or published on the network.
 
+.. Do we really want to talk about NC4 (since it's rather old) ?-)
+   OTOH, mentioning KDE is good as it's a "desktop enviroment" (not 
+   just a single "program") [HH]
+
 We have extended KDE and Netscape Communicator 4 to understand
 our experimental URIs. Most other systems can use Storm 
 through an HTTP gateway.
@@ -61,24 +72,28 @@
 on the desktop is broken links. A user receiving
 hyperlinked documents by email, for example, would have to reconstruct
 the original directory structure; otherwise the links
-won't work.
+will not work.
+
+.. Include to the paragraph above ?
+   "A major reason is that links break when documents are moved 
+   around or sent by mail." [HH]
 
 .. using location-independent identifiers for
    non-breaking links:
 
 If desktop documents could be refered to independently
-of their location, it would be possible to make
-non-breaking links to them. When a document is published
+of their location, it would be feasible to make
+non-breaking links to them: When a document is published
 on the Web, it would have the same URI as on the
-author's desktop. When a link to a document is emailed,
+author's desktop; when a link to a document is emailed,
 the receiver could follow the link as long as their
-computer can find the linked document-- on its local
+software can locate the linked document-- on its local
 harddisk, attached to another email, or on the
 public Internet.
 
 .. Freenet's cryptographical identifiers:
 
-Location-independent identifiers aren't a new idea.
+Location-independent identifiers are not a new idea.
 In Freenet [freenet-ieee]_, an anonymous peer-to-peer
 publication system, *cryptographic hashes* [bakhtiari95cryptographic]_
 are used to identify versions of documents. Hashes
@@ -112,7 +127,12 @@
 rendered this assumption obsolete. Distributed hashtables (DHTs)
 
[malkhi02viceroy-andalso-maymounkov02kademlia-andalso-ratnasamy01can-andalso-stoica01chord-andalso-zhao01tapestry]_
 
 allow location-independent identifiers
-to be resolved on a global scale.
+to be resolved on a global scale. In fact, authors argue in 
+[balakrishnan03semanticfree]_ that DHTs are suitable for the next generation 
+Reference Resolutions Services (RRS) [#]_.
+
+.. [#] Domain Name System (DNS) [rfc1101]_ is a widely used RRS 
+   system in the Internet.
 
 .. can be used to implement external links, backlinks &c:
 
@@ -157,9 +177,10 @@
 
 Browsers and applications can access Storm either
 by using the Java library directly or through an
-HTTP gateway, which, given a Storm URN, finds and
-returns the associated file. Documents can be
-uploaded into Storm through the gateway, using HTTP PUT.
+HTTP gateway, which locates and
+returns the associated file when a Storm URN is given. 
+Documents can be uploaded into Storm through the gateway, 
+using HTTP PUT.
 
 .. Applications we are integrated with:
 
@@ -173,11 +194,11 @@
 .. OpenOffice can load from http gateway
    (needs more complete WebDAV impl to save):
 
-The Emacs text editor doesn't understand Storm
+The Emacs text editor does not understand Storm
 URNs yet, but can load and save documents in
-Storm using the HTTP gateway. OpenOffice.org
+Storm using the HTTP gateway. OpenOffice.org software
 can load documents through the HTTP gateway,
-but cannot save changes, because the gateway
+but cannot save changes, since the gateway
 does not yet support WebDAV (HTTP-based distributed
 authoring and versioning).
 
@@ -203,7 +224,7 @@
 This may help in making hyperlinks between desktop
 documents more convenient.
 
-A distributed hashtable is used to find published documents.
+A distributed hashtable is used to locate published documents.
 While the core of Storm has been in use for almost
 three years, the peer-to-peer subsystem has only recently
 been implemented.