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: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/storm article.rst
Date: Sat, 15 Feb 2003 12:43:40 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 12:43:40

Modified files:
        storm          : article.rst 

Log message:
        twid

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.186 manuscripts/storm/article.rst:1.187
--- manuscripts/storm/article.rst:1.186 Sat Feb 15 12:41:07 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 12:43:40 2003
@@ -1103,11 +1103,11 @@
 
 One possibility is to take an existing system
 (with features outside the focus of Gzz)
-that implements strict versioning, and to modify it to use Storm for storage. 
+which implements strict versioning, and to modify it to use Storm for storage. 
 A candidate is the object-oriented Web publishing environment Zope [zope]_, 
 which is Free Software and stores everything by default as diffs to
-a (flat file) database. Another way is studying the applicability of the 
-open hypermedia protocol (OHP) [reich-davis99-ohp].
+a (flat file) database. The
+open hypermedia protocol (OHP) may be another possibiliy [reich-davis99-ohp].
 
 Besides these issues with the backend, we are facing user interface issues
 as well -- for example the conventions for listing, moving and deleting




reply via email to

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