mirror of
https://github.com/tahoe-lafs/tahoe-lafs.git
synced 2024-12-19 04:57:54 +00:00
relnotes.txt reflow column width and editing
This commit is contained in:
parent
0971d67bdf
commit
5fa3a625d9
58
relnotes.txt
58
relnotes.txt
@ -28,25 +28,28 @@ with v0.4.)
|
|||||||
WHAT IS IT GOOD FOR?
|
WHAT IS IT GOOD FOR?
|
||||||
|
|
||||||
The source code that we are releasing is the current working prototype for
|
The source code that we are releasing is the current working prototype for
|
||||||
Allmydata's next-generation product. This release is targeted at hackers and
|
Allmydata's next-generation product. This release is targeted at hackers
|
||||||
users who are willing to use a minimal, text-oriented web user interface.
|
and users who are willing to use a minimal, text-oriented web user
|
||||||
|
interface.
|
||||||
|
|
||||||
This software is not yet recommended for storage of highly confidential data
|
This software is not yet recommended for storage of highly confidential data
|
||||||
nor for important data which is not otherwise backed up, but it is useful for
|
nor for important data which is not otherwise backed up, but it is useful
|
||||||
experimentation, prototyping, and extension.
|
for experimentation, prototyping, and extension.
|
||||||
|
|
||||||
This release of Allmydata-Tahoe marks the first version which is be suitable
|
This release of Allmydata-Tahoe is suitable for Use Case #2: "groups of
|
||||||
for Use Case #2: "groups of friends who want to share backup and
|
friends who want to share backup and file-sharing" (see the wiki page
|
||||||
file-sharing" (see the wiki page "UseCases": [3]). It is easy to set up a
|
"UseCases": [3]). It is easy to set up a private grid which is securely
|
||||||
private grid which is securely shared among a specific, limited set of
|
shared among a specific, limited set of friends. Files uploaded to this
|
||||||
friends. Files uploaded to this shared grid will be available to all
|
shared grid will be available to all friends, even when some of the
|
||||||
friends, even when some of the computers are unavailable.
|
computers are unavailable. It is also easy to use a public grid, but to
|
||||||
|
encrypt individual files and directories so that only intended recipients
|
||||||
|
can read them.
|
||||||
|
|
||||||
|
|
||||||
LICENCE
|
LICENCE
|
||||||
|
|
||||||
Tahoe is offered under the GNU General Public License (v2 or later), with the
|
Tahoe is offered under the GNU General Public License (v2 or later), with
|
||||||
added permission that, if you become obligated to release a derived work
|
the added permission that, if you become obligated to release a derived work
|
||||||
under this licence (as per section 2.b), you may delay the fulfillment of
|
under this licence (as per section 2.b), you may delay the fulfillment of
|
||||||
this obligation for up to 12 months.
|
this obligation for up to 12 months.
|
||||||
|
|
||||||
@ -86,11 +89,12 @@ HACKING AND COMMUNITY
|
|||||||
Please join the mailing list [7] to discuss the ideas behind Tahoe and
|
Please join the mailing list [7] to discuss the ideas behind Tahoe and
|
||||||
extensions of and uses of Tahoe. Patches that extend and improve Tahoe are
|
extensions of and uses of Tahoe. Patches that extend and improve Tahoe are
|
||||||
gratefully accepted -- roadmap.txt shows the next improvements that we plan
|
gratefully accepted -- roadmap.txt shows the next improvements that we plan
|
||||||
to make. You can browse the revision control history, source code, and issue
|
to make and CREDITS lists the names of people who've contributed to the
|
||||||
tracking at the Trac instance [8]. Please see the buildbot [9], which shows
|
project. You can browse the revision control history, source code, and
|
||||||
how Tahoe builds and passes unit tests on each checkin, and the code coverage
|
issue tracking at the Trac instance [8]. Please see the buildbot [9], which
|
||||||
results [10] and percentage-covered graph [11], which show how much of the
|
shows how Tahoe builds and passes unit tests on each checkin, and the code
|
||||||
Tahoe source code is currently exercised by the test suite.
|
coverage results [10] and percentage-covered graph [11], which show how much
|
||||||
|
of the Tahoe source code is currently exercised by the test suite.
|
||||||
|
|
||||||
|
|
||||||
NETWORK ARCHITECTURE
|
NETWORK ARCHITECTURE
|
||||||
@ -100,12 +104,12 @@ server called an "introducer" is used to discover other peers with which to
|
|||||||
connect.
|
connect.
|
||||||
|
|
||||||
To store a file, the file is encrypted and erasure coded, and each resulting
|
To store a file, the file is encrypted and erasure coded, and each resulting
|
||||||
share is uploaded to a different peer. The secure hash of the encrypted file
|
share is uploaded to a different peer. The secure hash of the encrypted
|
||||||
and the encryption key are packed into a URI, knowledge of which is necessary
|
file and the encryption key are packed into a URI, knowledge of which is
|
||||||
and sufficient to recover the file.
|
necessary and sufficient to recover the file.
|
||||||
|
|
||||||
To fetch a file, starting with the URI, a subset of shares is downloaded from
|
To fetch a file, starting with the URI, a subset of shares is downloaded
|
||||||
peers, the file is reconstructed from the shares, and then decrypted.
|
from peers, the file is reconstructed from the shares, and then decrypted.
|
||||||
|
|
||||||
A single distinct server called a "vdrive server" maintains a global mapping
|
A single distinct server called a "vdrive server" maintains a global mapping
|
||||||
from pathnames/filenames to URIs.
|
from pathnames/filenames to URIs.
|
||||||
@ -115,11 +119,11 @@ inherent in this version. In particular, the completely-connected property
|
|||||||
of the grid and the requirement of a single distinct introducer and vdrive
|
of the grid and the requirement of a single distinct introducer and vdrive
|
||||||
server limits the possible size of the grid. We have plans to loosen these
|
server limits the possible size of the grid. We have plans to loosen these
|
||||||
limitations (see roadmap.txt). Currently it should be noted that the grid
|
limitations (see roadmap.txt). Currently it should be noted that the grid
|
||||||
already depends as little as possible on the accessibility and correctness of
|
already depends as little as possible on the accessibility and correctness
|
||||||
the introduction server and the vdrive server. Also note that the choice of
|
of the introduction server and the vdrive server. Also note that the choice
|
||||||
which servers to use is easily configured -- you should be able to set up a
|
of which servers to use is easily configured -- you should be able to set up
|
||||||
private grid for you and your friends almost as easily as to connect to our
|
a private grid for you and your friends almost as easily as to connect to
|
||||||
public test grid.
|
our public test grid.
|
||||||
|
|
||||||
|
|
||||||
SOFTWARE ARCHITECTURE
|
SOFTWARE ARCHITECTURE
|
||||||
|
Loading…
Reference in New Issue
Block a user