small edit
[Imported from Trac: page ServerSelection, version 7]
parent
785ab20f0e
commit
c4e8d84c94
|
@ -2,7 +2,7 @@
|
||||||
|
|
||||||
Different users of Tahoe-LAFS have different desires for "Which servers should I upload which shares to?".
|
Different users of Tahoe-LAFS have different desires for "Which servers should I upload which shares to?".
|
||||||
|
|
||||||
* allmydata.com wants to upload to a random selection, evenly distributed among servers which are not full; This is, unsurprisingly, what Tahoe v1.4 currently does.
|
* allmydata.com wants to upload to a random selection, evenly distributed among servers which are not full; This is, unsurprisingly, what Tahoe v1.5 currently does.
|
||||||
* Brian has mentioned that an allmydata.com-style deployment might prefer to have the servers with more remaining capacity receiving more shares, thus "filling up faster" than the servers with less remaining capacity.
|
* Brian has mentioned that an allmydata.com-style deployment might prefer to have the servers with more remaining capacity receiving more shares, thus "filling up faster" than the servers with less remaining capacity.
|
||||||
* Kevin Reid wants, at least for one of his use cases, to specify several servers each of which is guaranteed to get at least K shares of each file, in addition to potentially other servers also getting shares.
|
* Kevin Reid wants, at least for one of his use cases, to specify several servers each of which is guaranteed to get at least K shares of each file, in addition to potentially other servers also getting shares.
|
||||||
* Shawn Willden wants, likewise, to specify a server (e.g. his mom's PC) which is guaranteed to get at least K shares of certain files (the family pictures and movies files).
|
* Shawn Willden wants, likewise, to specify a server (e.g. his mom's PC) which is guaranteed to get at least K shares of certain files (the family pictures and movies files).
|
||||||
|
|
Loading…
Reference in a new issue