Context Navigation

Changes between Initial Version and Version 1 of Ticket #3931

initial	v1
13	13	This is just the list that's obvious from reading the names of its methods.
14	14
15		Most of the logic for most of these things is already implement by something other than `_Client`. However, `_Client` ties them all together in an obligatory "super object". Much of the functionality can be disabled - but only through the very awkward interface of the bytes in a `tahoe.cfg` file.
	15	Most of the logic for most of these things is already implemented by something other than `_Client`. However, `_Client` ties them all together in an obligatory "super object". Much of the functionality can be disabled - but only through the very awkward interface of the bytes in a `tahoe.cfg` file.
16	16
17	17	Instead of making `tahoe.cfg` the only control structure for what `_Client` does and does not do, we should arrange to have a convenient Python API that allows for composition of functionality. For starters, this could exactly mirror the capabilities of `tahoe.cfg` (and should, in fact, be the API that the contents of `tahoe.cfg` drives). The point would be to make it easier to make these choices from Python code - without a trip through an ini-style configuration file.