[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/storm article.rst
From: |
Tuomas J. Lukka |
Subject: |
[Gzz-commits] manuscripts/storm article.rst |
Date: |
Sat, 15 Feb 2003 14:05:34 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Changes by: Tuomas J. Lukka <address@hidden> 03/02/15 14:05:34
Modified files:
storm : article.rst
Log message:
twids
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/article.rst.diff?tr1=1.204&tr2=1.205&r1=text&r2=text
Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.204 manuscripts/storm/article.rst:1.205
--- manuscripts/storm/article.rst:1.204 Sat Feb 15 14:01:10 2003
+++ manuscripts/storm/article.rst Sat Feb 15 14:05:34 2003
@@ -485,11 +485,11 @@
===================
In Storm, all data is stored
-as *blocks*, byte sequences identified by a SHA-1
+as *blocks*, immutable byte sequences identified by a SHA-1
cryptographic content hash [fips-sha-1]_.
Purely a function of a block's content, block ids
are completely independent of network location.
-Blocks have a similar granularity
+Blocks have a similar or somewhat finer granularity
as regular files, but they are immutable, since any change to the
byte sequence would change the hash (and thus create a different block).
Mutable data structures are built on top of the immutable blocks
@@ -521,7 +521,7 @@
web cache [iyer02squirrel]_; however, downloads can be
from *any* peer since the source does not need to be trusted.
On the other hand, there are privacy
-concerns with exposing one's browser cache to the outside world.
+concerns with exposing one's cache to the outside world.
To replicate all data from computer A
on computer B, it suffices to copy all blocks from A to B that B
@@ -531,7 +531,7 @@
each version will be stored in its own block with its own id.
In contrast, a system based on mutable resources
has to use more advanced schemes, for example merging the changes
-done to a document at A or B. (Merging is still be necessary
+done to a document at A or B. (Merging is still necessary
when a user wants to incorporate a set of changes, but not
required at replication time.)
- [Gzz-commits] manuscripts/storm article.rst, (continued)
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst,
Tuomas J. Lukka <=
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Tuomas J. Lukka, 2003/02/15
- [Gzz-commits] manuscripts/storm article.rst, Benja Fallenstein, 2003/02/15