Distribute shares in another determinate way

[Shu Lin]

Paul,

Thanks a lot for the information! The feature we are looking for is exact
ticket #573.

Actually, if I have a team can build such an application mentioned in
ticket #573, which is maintaining a server capability mapping and able to
submit per upload server preference. Can Tahoe team do define the interface
mentioned in #573?

If Tahoe team has no bandwidth on this, we are willing to help out on this
issue. Just looking for a good way to coordinate the effort. :-)

Thanks a lot,
-Shu


On Mon, Dec 29, 2014 at 9:25 AM, Paul Rabahy <prabahy at gmail.com> wrote:

> Currently there is not, but this has been discussed and it appears that
> there is a general agreement that enhancing storage node selection is a
> good idea.
>
> Related tickets:
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/467
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/573
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1838
> https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2059
>
>
> On Mon, Dec 29, 2014 at 11:59 AM, Shu Lin <linshu at gmail.com> wrote:
>
>> Hi Tahoe team,
>>
>> From current implementation, it seems Tahoe picks up servers based on k,
>> n and happiness parameters. I am wondering if Tahoe can provide an
>> interface or framework to hook up a 3rd party server distribution
>> algorithm, which might allow 3rd party to hook up some other determinate
>> server distribute algorithms, such as server location or network bandwidth
>> as preference?
>>
>> Thanks a lot,
>> -Shu
>>
>> _______________________________________________
>> tahoe-dev mailing list
>> tahoe-dev at tahoe-lafs.org
>> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20141229/c4fb13b9/attachment.html>