[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/05 17:57:10

Modified files:
        storm          : article.rst 

Log message:
        org use cases

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.92 manuscripts/storm/article.rst:1.93
--- manuscripts/storm/article.rst:1.92  Wed Feb  5 17:40:01 2003
+++ manuscripts/storm/article.rst       Wed Feb  5 17:57:10 2003
@@ -44,7 +44,7 @@
 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. 
-Furthermore, the same document is independently modified 
+Furthermore, the same document may be independently modified 
 on two (or more) unconnected, separete systems. We use
 *data mobility* as a collective term for the movement of documents
 between computers (or locations on one computer, such as folders),
@@ -60,15 +60,27 @@
 make these issues much easier to deal with, since data
 can be recognized whereever it is moved. 
 
-Examples for data mobility include:
+Examples for data mobility include today:
 
-- train collaboration
-- email attachment synchronization of versions
-- publication, hosting on own computer
-- comments and links on published document
-- travelling with laptop, off-line work
-- load
-- reconnecting the laptop after off-line work
+- sharing versions (email attachment, disk) -> versioning
+- cvs-like central sync point(s) -> versioning
+- off-line work (dialup, laptop/cellphone/pda) -> links
+- publication -> links
+- mirroring -> links
+- downloading -> links, versioning if modified after download
+- moving between own systems (desktop/laptop, work/home) ->
+  versioning, links
+- web archive -> links, versioning (past versions)
+
+Future visions:
+
+- downloading from others' cache/permanent storage (load balancing) ->
+  links
+- hosting on own computer. others mirror -> links
+- ad-hoc sharing (train, cafe) -> links
+
+.. not really data mobility:
+   - comments and links on published document
 
 .. The design also allows for
    automatic balancing of the load, which occurs in location-dependent
@@ -110,6 +122,10 @@
 Gzz provides a general platform for building hypermedia applications upon.
 On top of Storm, we have built a system for storing mutable, versioned data
 and an implementation of Xanalogical storage [ref].
+
+XXX {The current implementation has been used for local disk storage
+and central sync point. Our p2p impl is in a very early stage, and
+we have not yet implemented ad-hoc sharing (aka train collaboration).]
 
 .. [General figure of Storm, i.e. application layer, storm layer, 
    netowork layer ? -Hermanni]