[Gzz-commits] manuscripts/storm article.rst

[Toni Alatalo]

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

Modified files:
        storm          : article.rst 

Log message:
        began work on evaluation/discussion/open_issues

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.163 manuscripts/storm/article.rst:1.164
--- manuscripts/storm/article.rst:1.163 Sat Feb 15 10:01:00 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 10:19:06 2003
@@ -1105,11 +1105,24 @@
 [At the end of this section ? -Hermanni]
 When Xanalogical storage is not applied, using Storm as a
 replacement/equivalent of a conventional file and versioning system is
-trivial?    
+trivial?
+
+Besides the selected issues discussed above, a few remarks about further
+evaluation of Storm follow. From a security point of view, the fact that all
+data is stored in immutable blocks has obvious benefits for reliablity (data
+is never overwritten). By way of using of SHA-1 cryptocraphic content hashes
+as identifiers, verifyability is another benefit. As for usability, the ease
+of replication and caching combined with location-independent identifiers
+enable several improvements, including the possibility to keep on working on
+shared documents even when there is no or an unreliable network connection.
+
+There are, however, several open issues that are discussed next.
 
 
 7.2 Status, open issues and future work
 ---------------------------------------
+
+
 
 [worth to mention, security in general ? -Hermanni]
 1) Open issue: We want to be able