I know that the current introducer client is designed for another object, say a repairer, to call get_permuted_peers(si), but I would like to make it clear to the reader that the immutable repairer object starts with a given set of connections to storage servers and does not dynamically discover new storage servers during its run. There is a plausible but bad alternate design in which the repairer uses the introducer client to get dynamic updates of the set of servers to use, and I want to make it clear to the reader that immutable repairer doesn't use that technique.
Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
