[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/01/30 10:24:25

Modified files:
        storm          : article.rst 

Log message:
        review of scenario/use cases, after the design has been presented. just 
a sketch yet with open questions etc.

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.58 manuscripts/storm/article.rst:1.59
--- manuscripts/storm/article.rst:1.58  Wed Jan 29 06:28:20 2003
+++ manuscripts/storm/article.rst       Thu Jan 30 10:24:25 2003
@@ -169,7 +169,7 @@
 3. B publishes the document on the Internet, hosting on her laptop only.
 
 4. A and some other people view and comment the document with their
-machines.
+machines, also bookmarking it and linking from their own pages (e.g. blogs).
 
 5. B travels with the laptop, taking it off-line.
 
@@ -396,6 +396,39 @@
 In broadcasting approach, implementations' differences mostly lie in the 
 *structural level* of overlay network, i.e. super peers and peer clusters.
 
+Review of the use cases: what does storm in each?
+-------------------------------------------------
+(where&how to put this, if use cases are used like this at all?)
+
+1. live meeting:
+Documents have been assigned block-ids (and urns?) at creation.
+Pools that are shared / set visible for the other user show over the
+network. (...)
+
+2. syncing via a remote connection after working separately:
+Both new versions are actually diffs to the original. How do they merge?
+
+3. publising on/from the laptop:
+B sets the document public (how that is done depends on UI implementation),
+.. how does it go with storm, then?
+
+4. A and other people viewing, commenting, bookmarking, linking:
+When someone views the document, the system retrieves the datablock.
+Comments may be new entities(?) linking to it, editing would create a new
+version as a diff as a new datablock with a new guid. Bookmarks and links to
+the original are made to the ID of the original, with no trace of the
+location (originally B's laptop).
+
+5. When B takes her laptop off-line, the searches for the ID of her (and
+A's) Document simply result pointing at the other copies (e.g. on A's
+machine).
+
+6. Increasing traffic: The peer-to-peer network can automatically share the
+load, as popular items get replicated and further delivered from different
+hosts. (does storm actually do this / is it aimed at this?)
+
+7. When B reconnects, can check comments to the Document etc? How does that
+happen?
 
 8. Experience and future directions
 ===================================