Hello huang jun. Welcome to the tahoe-dev mailing list.

On Fri, Mar 23, 2012 at 8:55 AM, huang jun <hjwsm1...@gmail.com> wrote:
> hi,all
>  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?

https://tahoe-lafs.org/~zooko/lafs.pdf

http://code.google.com/p/nilestore/wiki/TahoeLAFSBasics

https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/docs/specifications/mutable.rst

https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Capabilities

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.

>  currently, which peer selection alrogithm does it performed?
> Tahoe2ServerSelector?

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
`docs/specifications/servers-of-happiness.rst`_.

The source code is in `allmydata/immutable/upload.py`_ (for immutables
only, by the way).

Regards,

Zooko

.. _docs/specifications/servers-of-happiness.rst:
https://tahoe-lafs.org/trac/tahoe-lafs/browser/git/docs/specifications/servers-of-happiness.rst
.. _wiki:ServerSelection:
https://tahoe-lafs.org/trac/tahoe-lafs/wiki/ServerSelection
.. _wiki:TahoeTwo: https://tahoe-lafs.org/trac/tahoe-lafs/wiki/TahoeTwo
.. _allmydata/immutable/upload.py:
https://tahoe-lafs.org/trac/tahoe-lafs/browser/src/allmydata/immutable/upload.py?rev=4114#L131
_______________________________________________
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev

Reply via email to