[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2759: separate Tub per server connection

[Tahoe-LAFS]

#2759: separate Tub per server connection
------------------------------+-----------------------
     Reporter:  warner        |      Owner:
         Type:  enhancement   |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-network  |    Version:  1.10.2
   Resolution:                |   Keywords:
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by leif):

 I like this `connections.yaml` layout a lot!

 Maybe we should have a top-level default `connection_types` key too, to
 avoid repeating ourselves in each server and introducer definition? (When
 it exists, the server and introducer-level `connection_types` dictionary
 should be used in place of the default dictionary, not in addition to it).

 I'm a little hesitant about requiring (local) introducer nicknames because
 people will have to make one up and it'll probably often end up being "My
 Introducer" or something like that, but it will certainly make the
 introducer list on the welcome page easier to understand when there are
 several introducers. The nickname can also be used as the filename for the
 introducer's yaml announcement cache.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2759#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage