[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 warner):

 Oh, I like that. It sounds like the simplest thing to implement, and
 mostly retains the current behavior.

 We need to think through how replacement announcements get made: I think
 announcements have sequence numbers, and highest-seqnum wins. If we write
 all announcements into the cache (as opposed to rewriting the cache each
 time with only the latest announcement for each server), then we'll have
 lots of old seqnums in the file, but we can filter those out when we read
 it.

 Also there's a small window when the introducer restarts, before the
 servers have reconnected to it, when it won't be announcing very much. Our
 client will erase its cache when it reconnects, and we'll have a small
 window when the cache is pretty empty. However if the client is still
 running (it hasn't bounced), it will still remember all the old
 announcements in RAM, so those connections will stay up. And if it does
 bounce, then it's no worse than it was before the cache.

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