[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

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

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.205&tr2=1.206&r1=text&r2=text

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.205 manuscripts/storm/article.rst:1.206
--- manuscripts/storm/article.rst:1.205 Sat Feb 15 14:05:34 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 14:13:05 2003
@@ -294,7 +294,7 @@
 by sending it to the peer responsible for the key. Both approaches
 use an application-level overlay network for routing.
 
-While broadcasting systems' performance is not always even linear, DHTs' 
performance
+While broadcasting systems' performance can be worse than linear, DHTs' 
performance
 usually has log-like bounds in the number of peers 
 for *all* internal operations [#]_. This scalability is
 what makes global searches feasible in DHTs. In broadcasting approaches,
@@ -302,7 +302,7 @@
 only to a limited subset of the peers (bounded by the time-to-live),
 which means that searches in these systems are not truly global.
 
-[broadcasting's message population can grow as fast as O(n^2) -Hermanni]
+.. [broadcasting's message population can grow as fast as O(n^2) -Hermanni]
 
 .. [#] It's not clear whether *all* proposed DHT designs can preserve
    log-like properties when participants are heterogeneous and they 
@@ -572,14 +572,14 @@
 never overwrite existing data. When a bug causes an application
 to write malformed data, only the changes from one session
 will be lost; the previous version of the data will still
-be accessible [#]_. This makes Storm well suited as a basis
+be accessible. This makes Storm well suited as a basis
 for implementing experimental projects (such as ours, Gzz).
 Even production systems occasionally corrupt existing data
 when an overwriting save operation goes awry; for example,
 one of the authors has had this problem with
 Microsoft Word many times.
 
-.. [#] Unfortunately, efficient versioned storage (Section 6)
+.. (was footnote) Unfortunately, efficient versioned storage (Section 6)
    makes matters a little more complicated; still,
    the basic assertion holds.