Files
lightning/lightningd
Rusty Russell ee00c2c508 lightningd: remove peer->gossip_client_fd
We don't need to keep this around any more: by handing it to
subdaemons we ensure we'll close it if the peer disconnects, and we
also add code to get a new one on reconnection.

Because getting a gossip_fd is async, we re-check the peer state after
it gets back.  This is kind of annoying: perhaps if we were to hand
the reconnected peer through gossipd (with a flag to immediately
return it) we could get the gossip fd that way and unify the paths?

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-06-27 10:25:53 +09:30
..
2017-06-23 16:02:20 +09:30
2017-05-12 12:59:09 +02:00
2017-05-09 11:43:35 +09:30
2017-06-27 10:25:53 +09:30
2017-05-25 14:24:47 +09:30
2017-02-24 16:22:56 +10:30
2017-05-09 11:43:35 +09:30
2017-04-25 22:00:28 +02:00
2017-06-07 09:19:04 +09:30
2017-06-27 10:25:53 +09:30
2017-06-06 09:16:10 +09:30