[tahoe-lafs-trac-stream] [tahoe-lafs] #573: Allow client to control which storage servers receive shares

[tahoe-lafs]

#573: Allow client to control which storage servers receive shares
------------------------------------+-----------------------
     Reporter:  swillden            |      Owner:
         Type:  enhancement         |     Status:  closed
     Priority:  minor               |  Milestone:  undecided
    Component:  code-peerselection  |    Version:  1.2.0
   Resolution:  duplicate           |   Keywords:
Launchpad Bug:                      |
------------------------------------+-----------------------

Comment (by nejucomo):

 Replying to [comment:8 warner]:
 > Please take a look at #467, which is about a tahoe.cfg language for
 defining storage servers (instead of or in addition to using the
 Introducer), and attributes like how many shares should be sent to such
 servers.
 >
 > As Shawn pointed out, an important feature of this language is to say
 "do not send shares to myself, even if I'm running a storage server".
 >
 > I currently feel that #467 (specify the servers in tahoe.cfg) will be
 more useful to more people than (this) #573 (specify the servers in the
 webapi call), and easier to implement, if only because to take advantage
 of #573, people have to write an application which:
 >
 >  1. uses an as-yet-unwritten API to learn about a list of servers, or
 has such a list hard-coded into it
 >  1. speaks the tahoe webapi to pass the additional arguments, rather
 than using the existing CLI tools like 'tahoe backup'
 >
 > Whereas folks that are on a static friendnet (with perhaps some servers
 that are larger than others) can all use the same tahoe.cfg server-
 specification text and then use all their existing tahoe-enabled tools
 without change.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/573#comment:14>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage