docs: a couple of minor edits to NEWS and docs/architecture.txt

This commit is contained in:
Zooko O'Whielacronx 2009-07-20 18:41:12 -07:00
parent bf1e61c8f3
commit abd2ff6ba5
2 changed files with 9 additions and 8 deletions

5
NEWS
View File

@ -30,8 +30,9 @@ This version of Tahoe will tolerate directory entries that contain filecap
formats which it does not recognize: files and directories from the future.
Previous versions would fail badly, preventing the user from seeing or
editing anything else in those directories. These unrecognized objects can be
renamed and deleted, but obviously not read or written. This should improve
the user experience when we add new cap formats in the future. (#683)
renamed and deleted, but obviously not read or written. Also they cannot be
copied. This should improve the user experience when we add new cap formats in
the future. (#683)
** Bugfixes

View File

@ -6,12 +6,12 @@ OVERVIEW
At a high-level this system consists of three layers: the grid, the
filesystem, and the application.
The lowest layer is the "grid", a mapping from capabilities to data.
The capabilities are relatively short ascii strings, each used as a
reference to an arbitrary-length sequence of data bytes, and are like a
URI for that data. This data is encrypted and distributed across a
number of nodes, such that it will survive the loss of most of the
nodes.
The lowest layer is the "grid", a key-value store mapping from
capabilities to data. The capabilities are relatively short ascii
strings, each used as a reference to an arbitrary-length sequence of
data bytes, and are like a URI for that data. This data is encrypted and
distributed across a number of nodes, such that it will survive the loss
of most of the nodes.
The middle layer is the decentralized filesystem: a directed graph in
which the intermediate nodes are directories and the leaf nodes are