[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/01/28 12:04:29

Modified files:
        storm          : article.rst 

Log message:
        restructure as hemppah suggested

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.48 manuscripts/storm/article.rst:1.49
--- manuscripts/storm/article.rst:1.48  Tue Jan 28 05:14:58 2003
+++ manuscripts/storm/article.rst       Tue Jan 28 12:04:29 2003
@@ -20,17 +20,6 @@
 regard to hypermedia.
 [/maybe]
 
-In today's computing world, documents move quite freely between computers, 
being 
-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. 
-Often, the same document will be independently modified 
-on two unconnected systems. We describe 
-the partially implemented Storm design, 
-a storage system designed to cope with two problems
-raised by moving documents: Dangling links [refs stating problem], 
-and keeping track of alternative versions [refs stating problem].
-
 On the Web, documents are tightly bound to one location: they 
 cannot be moved to a different server without breaking links to them[#]_.
 It is the norm for hypermedia systems to bind documents to hosts,
@@ -56,6 +45,13 @@
 and, at least in its 1988 incarnation [ref Green] addressed data 
 based on the address of a server holding a 'master copy.'
 
+However, in today's computing world, documents move quite freely between 
computers, being 
+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. 
+Often, the same document will be independently modified 
+on two unconnected systems. 
+
 
 
 [Note: The following are my notes for what should be written,
@@ -125,6 +121,14 @@
 ->
 We present Storm (for *storage module*), a design which addresses the issues 
 we have described. 
+
+->
+We describe 
+the partially implemented Storm design, 
+a storage system designed to cope with two problems
+raised by moving documents: Dangling links [refs stating problem], 
+and keeping track of alternative versions [refs stating problem].
+
 
 The main contributions of this paper are...