ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-20 05:28:04 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Warn about ambiguities on "client" and "gateway" terms

Browse Source
This commit is contained in:
pataquets 2013-12-03 17:25:45 +01:00
parent 9e5080903e
commit 857d072ff4
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/about.rst
View File

@ -45,7 +45,15 @@ Here's how it works:
A "storage grid" is made up of a number of storage servers. A storage server A "storage grid" is made up of a number of storage servers. A storage server
has direct attached storage (typically one or more hard disks). A "gateway" has direct attached storage (typically one or more hard disks). A "gateway"
uses the storage servers and provides access to the filesystem over HTTP(S) uses the storage servers and provides access to the filesystem over HTTP(S)
or (S)FTP. or (S)FTP to tahoe clients.
Note that you can find gateway nodes referred sometimes as client nodes. The
Tahoe-LAFS architecture defines gateways as "nodes that provide access to
files residing in storage nodes". You can see "clients" also referring to
processes or programs connecting to a gateway node and performing operations
on the grid (for exemple, the CLI binary).
Gateways give access to files in the grid via protocols such as HTTP, FTP or
SFTP. So, the gateways act as "clients" to other storage nodes at the same
time that they are serving files to client programs (WebUI, (S)FTP clients).
Users do not rely on storage servers to provide *confidentiality* nor Users do not rely on storage servers to provide *confidentiality* nor
*integrity* for their data -- instead all of the data is encrypted and *integrity* for their data -- instead all of the data is encrypted and