[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo at Univ. of Oulu]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo at Univ. of Oulu <address@hidden>  03/01/21 
03:47:18

Modified files:
        storm          : article.rst 

Log message:
        added a paragraph on how collaborative use motivates this, to 
introduction

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.22 manuscripts/storm/article.rst:1.23
--- manuscripts/storm/article.rst:1.22  Mon Jan 20 09:52:17 2003
+++ manuscripts/storm/article.rst       Tue Jan 21 03:47:18 2003
@@ -49,6 +49,18 @@
 to a different computer, and after modifying the data on both systems,
 it should be easy to bring the two copies back in sync.
 
+Another motivation (right?) for the data sharing / data mobility is
+collaboration. Within an organization or a project group, there often is a
+shared file system, e.g. a file server in the local network, so that
+different people do not need their personal copies of the data but can work
+(synchronously) on the same items. Often, however, especially when
+crossing organizationary boundaries there is no access each-others'
+filesystems even though data is shared. In actual collaboration, where
+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.
+
 Our system allows documents and document content to be freely copied
 without breaking links. As long as a link and the documents
 it links are currently accessible, the link can be shown.