[tahoe-dev] [tahoe-lafs] #68: implement distributed introduction, remove Introducer as a single point of failure
tahoe-lafs
trac at tahoe-lafs.org
Mon Jul 5 12:25:36 PDT 2010
#68: implement distributed introduction, remove Introducer as a single point of
failure
------------------------------+---------------------------------------------
Reporter: lvo | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone: eventually
Component: code-network | Version: 0.2.0
Resolution: | Keywords: scalability availability introduction gsoc
Launchpad Bug: |
------------------------------+---------------------------------------------
Comment (by zooko):
Nice work! Now that there is a unit test we can start thinking about
actually committing these patches to trunk.
This test would notice if the code under test failed to read the
{{{.tahoe/introducers}}} config file correctly or failed to create an
!IntroducerClient for each one, right?
Now can you write a test (or extend the test you already wrote) to notice
if the code under test failed to subscribe to all of the introducers that
it knew about? For example, maybe the test would configure two introducers
in the {{{.tahoe/introducers}}} file, {{{mock.patch()}}} the
!IntroducerClient class, then instantiate the src/allmydata/client.py
{{{Client}}} class, then check that two mock !IntroducerClients got
created and that each of them had their {{{.subscribe_to()}}} method
called.
After that, I can't think of any way that your patch to
allmydata/client.py would have a bug which would not be caught by these
tests. Can you?
--
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/68#comment:27>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized file storage grid
More information about the tahoe-dev
mailing list