[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/01 20:59:46

Modified files:
        storm          : article.rst 

Log message:
        some closings

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.69 manuscripts/storm/article.rst:1.70
--- manuscripts/storm/article.rst:1.69  Sat Feb  1 17:24:52 2003
+++ manuscripts/storm/article.rst       Sat Feb  1 20:59:45 2003
@@ -541,7 +541,9 @@
 
 Review of the use cases: what does storm in each?
 -------------------------------------------------
-(where&how to put this, if use cases are used like this at all?)
+(where&how to put this, if use cases are used like this at all? 
+agreed with benja on irc that we might try this approach - hinting about the
+use cases early on and taking a detailed look later, in light of the design.)
 
 1. live meeting:
 Documents have been assigned block-ids (and urns?) at creation.
@@ -549,18 +551,23 @@
 network. (...)
 
 2. syncing via a remote connection after working separately:
-Both new versions are actually diffs to the original. How do they merge?
+Both new versions are actually diffs to the original. Merging is
+application-specific.
 
-3. publising on/from the laptop:
+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?
+i.e. putting in a published pool, which may reside locally or externally
+e.g. on a (dedicated) server that is "always-on". These public/private zones
+are an area where future research is needed, possibly related to rights and
+permissions etc. too.
 
 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).
+location (originally B's laptop). (more info about pointers here, and in the
+next one?)
 
 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
@@ -571,8 +578,8 @@
 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?
-
+happen? Index?
+ 
 8. Experience and future directions
 ===================================