[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

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

Modified files:
        storm          : article.rst 

Log message:
        collab. refs., beginnings of a limitations section: are there 
weaknesses in storm? ponder irc, live video

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.28 manuscripts/storm/article.rst:1.29
--- manuscripts/storm/article.rst:1.28  Tue Jan 21 08:27:15 2003
+++ manuscripts/storm/article.rst       Wed Jan 22 03:30:46 2003
@@ -59,7 +59,7 @@
 several individuals work on the same items -- possibly at the sametime --
 the data effectually forks. So similarly(?) to the the situation where a
 particular user has data on different computers, data needs to be kept in
-sync when there is collaboration.
+sync when there is collaboration. [cvs, (perforce, ..)]
 
 Our system allows documents and document content to be freely copied
 without breaking links. As long as a link and the documents
@@ -132,6 +132,21 @@
   (includes syncing, finding a document if available...)
 - Xanalogical structure 
   (includes versioning, non-breaking links etc.)
+
+Storm limitations/weaknesses:
+
+- what, actually?
+
+antont ponders: for files storm is ok, but how about:
+- irc? (latency?)
+- video? (throughput)
+
+and:
+.. multipoint live video? (both latency and throughput demands)
+
+* does it make sense to think of irc messages, and/or video frames, as
+datablocks .. or what?
+
   
 hemppah's comment on syncing term:
 I'd prefer term 'replication' instead of term syncing, when
@@ -326,11 +341,11 @@
  http://www.almaden.ibm.com/cs/people/bayardo/userv/
  http://www.almaden.ibm.com/cs/people/bayardo/userv/userv.html
 
-is this relevant:  P. Druschel and A. Rowstron. PAST: A largescale,
-persistent peer-to-peer storage utility. In IEEE, editor, Eighth IEEE
-Workshop on Hot Topics in Operating Systems (HotOS-VIII). May 20-23, 2001,
-Schloss Elmau, Germany, pages 75-80, 1109 Spring Street, Suite 300, Silver
-Spring, MD 20910, USA, 2001. IEEE Computer Society Press. ?
+P. Druschel and A. Rowstron. PAST: A largescale, persistent peer-to-peer
+storage utility. In IEEE, editor, Eighth IEEE Workshop on Hot Topics in
+Operating Systems (HotOS-VIII). May 20-23, 2001, Schloss Elmau, Germany,
+pages 75-80, 1109 Spring Street, Suite 300, Silver Spring, MD 20910, USA,
+2001. IEEE Computer Society Press.
 
 - Squirrel: a decentralized peer-to-peer web cache
 - Feasibility of a Serverless Distributed File System Deployed on an Existing 
Set of Desktop PCs
@@ -344,5 +359,5 @@
 - Semantic Overlay Networks for P2P systems (a p2p 'version' of Xanalogical 
transclusions)
 - Farsite Project (similar to CFS, PAST and Oceanstore)
 
-Comments on references:
-- Yes, PAST is relevant. It's very similar to CFS (and Oceanstore)
+There was a good paper and demo about synchronous collaboration in ht01, but
+is that out of scope here? (see pondering on limitations)