[tahoe-lafs-trac-stream] [tahoe-lafs] #1765: gossip-introducer should forget about old nodes somehow

[tahoe-lafs]

#1765: gossip-introducer should forget about old nodes somehow
--------------------------------+--------------------
     Reporter:  warner          |      Owner:  warner
         Type:  enhancement     |     Status:  new
     Priority:  normal          |  Milestone:  soon
    Component:  code-nodeadmin  |    Version:  1.9.1
   Resolution:                  |   Keywords:
Launchpad Bug:                  |
--------------------------------+--------------------

Comment (by zooko):

 Replying to [comment:3 warner]:
 >
 > The only concern I can think of is that partial connectivity
 > might prevent a new client from learning about nodes that they could
 > normally connect to. In particular, could this interact with NAT in some
 > way that might produce a less-connected grid than our current central
 > Introducer? I don't think so, but I'd have to study it more.

 Hrm. This idea of gossip conflicts with my idea that each server should
 attempt to connect to all clients -- and only to clients -- and that each
 client should attempt to connect to all servers -- and only to servers
 (#344, #1086).

 It would also interact somewhat poorly with #444

 In fact, why do we need to switch from introducers to gossip at all? Could
 we finish the rest of the #466 new-introduction-protocol and related
 accounting infrastructure while leaving the current centralized introducer
 (or the #68 multiple introducers) alone?

 I think this discussion needs to move to the mailing list...

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1765#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage