[tahoe-dev] User Specification of Servers (#467)
mjberger at stanford.edu
Thu Apr 18 04:55:52 UTC 2013
Ah alright, thanks for letting me know Zooko. I'll start reading through
Kevan's thesis to see if that's something I'd be interested in.
Daria, thanks for linking me to the ticket. And yes search works for me now.
On Wed, Apr 17, 2013 at 8:10 PM, Daira Hopwood (formerly David-Sarah) <
davidsarah at leastauthority.com> wrote:
> On 17/04/13 03:35, Mark Berger wrote:
> > I am interested in implementing the idea of prioritizing storage servers
> before consulting
> > the
> > introducer (https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467 and
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/573 ).
> > The implementation would ensure that shares are always uploaded to a
> specific server. For
> > example, in a network of local computers with an AWS backend node shares
> may not
> > necessarily be populated to AWS. However, AWS is more reliable than the
> local computers
> > and not susceptible to the same environmental disaster as the local
> network. Therefore it
> > makes sense to ensure that shares are always uploaded to AWS and not
> > distributed pseudo-randomly. Is this the core idea behind ticket #467?
> That's one possible case (and a very common one), yes.
> > Also, is the aspect of populating the node's server list to the
> introducer still relevant?
> That is not required for a basic implementation of #467.
> > I remember reading that code has been written to replace the introducer,
> but I can't seem
> > to find the ticket anymore.
> > I am having trouble searching for tickets (Error: Darcs execution
> Is that working again now? If not, how are you searching?
> Daira Hopwood ⚥ (formerly David-Sarah)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tahoe-dev