gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/storm article.rst


From: Toni Alatalo
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Thu, 06 Feb 2003 07:06:44 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo <address@hidden>   03/02/06 07:06:41

Modified files:
        storm          : article.rst 

Log message:
        an attempt to close an open end, was the original thought there 
something completely different?

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.103 manuscripts/storm/article.rst:1.104
--- manuscripts/storm/article.rst:1.103 Thu Feb  6 03:12:25 2003
+++ manuscripts/storm/article.rst       Thu Feb  6 07:06:41 2003
@@ -9,7 +9,7 @@
 Motivations and potential solutions are reviewed, and a design for 
 a system being developed for (these purposes) is presented. 
 The design and a partial implementation of it is evaluated 
-in light of use cases from a realistic(?) scenarios. Open issues are 
+in light of use cases from realistic(?) scenarios. Open issues are 
 discussed, and the areas for future work in such as 
 interoperability, scalability and security is identified.
 
@@ -96,6 +96,8 @@
 synchronizing irregularly with a central server (as in CVS [ref]),
 a network (as in Lotus Notes [ref]) or directly with each other 
 (as in Groove[?] [ref]). In each of these cases, a user should be able
+to work on the version at hand and then either merge it with others 
+or fork to a different branch.
 
 In this paper, we present Storm (for *storage module*), a design 
 dealing with these issues. Storm is a library




reply via email to

[Prev in Thread] Current Thread [Next in Thread]