[tahoe-dev] tahoe-dev Digest, Vol 60, Issue 27
hjwsm1989 at gmail.com
Mon Mar 26 03:01:01 UTC 2012
> Date: Fri, 23 Mar 2012 11:08:02 -0600
> From: "Zooko Wilcox-O'Hearn" <zooko at zooko.com>
> To: Tahoe-LAFS development <tahoe-dev at tahoe-lafs.org>
> Subject: Re: [tahoe-dev] questions about keys in tahoe
> <CANdZDc5cPf0vmz0GfE5FQNxfFOyouj6_6918wGHVgN7kpMRgZQ at mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
> Hello huang jun. Welcome to the tahoe-dev mailing list.
> On Fri, Mar 23, 2012 at 8:55 AM, huang jun <hjwsm1989 at gmail.com> wrote:
>> ?we are confused about that
>> ? ? ?1) private_key ---> write_key ---> read_key ---> storage index
>> ? ? ?2) public_key ------> verification hash key
>> ?where did the private_key and public_key comes from?
> Have you already seen these documents?
> If you did not previously see those documents, please let us know
> which ones you did not already see. We are trying to learn how to
> organize the documentation so that people can find the information
> that they seek.
i didn't read the eassy and read almost all document in
https://tahoe-lafs.org/trac/tahoe-lafs but not wiki,
>> ?currently, which peer selection alrogithm does it performed?
> It is a lot like the Tahoe2ServerSelector described on
> `wiki:ServerSelection`_ and `wiki:TahoeTwo`_, but it has been extended
> by the notion of "servers of happiness", which are documented in
> The source code is in `allmydata/immutable/upload.py`_ (for immutables
> only, by the way).
thanks, and is there any comparability between tahoe select algorithm
and RAID in specified operation like 'add a disk' to the storage
> .. _docs/specifications/servers-of-happiness.rst:
> .. _wiki:ServerSelection:
> .. _wiki:TahoeTwo: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeTwo
> .. _allmydata/immutable/upload.py:
More information about the tahoe-dev