[Imported from Trac: page Doc, version 3]
parent
e85aedb219
commit
0484d966ba
5
Doc.md
5
Doc.md
|
@ -12,7 +12,10 @@
|
|||
|
||||
## Detailed Design Docs
|
||||
* [TahoeIssues](TahoeIssues)/FileTree, explaining how mutable, shareable, private directories are implemented (which requires interesting crypto)
|
||||
* [TahoeIssues](TahoeIssues)/PeerSelection, explaining how a Tahoe node chooses which other nodes to use for uploading and downloading files (which raises some unsolved issues in balancing scalability, robustness, performance, and simplicity)
|
||||
* [TahoeIssues](TahoeIssues)/FileEncoding, explaining how we turn files into shares, with verifiable hashes; This is mostly concerned with chunking and Merkle trees.
|
||||
* [TahoeIssues](TahoeIssues)/ShareEncoding, explaining how we turn a chunk into shares: Reed-Solomon, FEC, that stuff
|
||||
|
||||
## Outstanding Issues
|
||||
* [TahoeIssues](TahoeIssues)/PeerSelection, explaining how a Tahoe node chooses which other nodes to use for uploading and downloading files (which raises some unsolved issues in balancing scalability, robustness, performance, and simplicity)
|
||||
* [TahoeIssues](TahoeIssues)/ChangingFilesWhileCopyingThem : what are the semantics of the "upload" action? the upload takes
|
||||
non-zero time: what happens if the file is changed during that time?
|
||||
|
|
Loading…
Reference in a new issue