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

[Tahoe-LAFS]

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

Comment (by dawuud):

 09:33 < warner> dawuud: I haven't looked at the branch recently, so maybe
 you already did it this way, but I think the first step would
                 be a single (merging + test-passing) PR that only adds Tub
 creation to the NativeStorageServer, and doesn't make any
                 changes to the Introducer or adds the yaml stuff
 09:34 < warner> I think that's something which would be ok to land on it's
 own, and ought not to break anything
 09:35 < warner> and wouldn't change user-visible behavior (mostly), so
 wouldn't require a lot of docs or study
 09:35 < warner> step 2 is probably to have the introducer start writing to
 the yaml file, but not have anything which reads from it yet
 09:36 < warner> step 3 would be reading from the yaml file too, but still
 have exactly one introducer
 09:36 < warner> step 4 is to add the override file (but still the only
 permissible connection type is "tcp")
 09:37 < warner> step 5 is to add multiple/zero introducers
 09:37 < warner> step 6 is to add tor and the allowed-connection-types
 stuff

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