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 14:53:24 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 14:53:24

Modified files:
        storm          : article.rst 

Log message:
        cut some important but not absolutely important stuff due to space 
constraints. 10pg now

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.218 manuscripts/storm/article.rst:1.219
--- manuscripts/storm/article.rst:1.218 Sat Feb 15 14:49:14 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 14:53:24 2003
@@ -1008,12 +1008,13 @@
 instead. At the cost of some storage space, this protects
 the user's data.
 
-Currently, Storm pool implementations do not know anything about diffs;
-all the functionality described here is implemented on top of them.
-For a networked system, however, it would be useful if a server
-could recreate version blocks before sending them to a client.
-Then, instead of transferring all the diffs, only the full version
-would have to be sent through the network.
+.. [this would be relevant, but is cut because of space constraints -b]
+   Currently, Storm pool implementations do not know anything about diffs;
+   all the functionality described here is implemented on top of them.
+   For a networked system, however, it would be useful if a server
+   could recreate version blocks before sending them to a client.
+   Then, instead of transferring all the diffs, only the full version
+   would have to be sent through the network.
 
 
 Discussion




reply via email to

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