mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-02-22 22:45:27 +01:00
Code Issues Projects Releases Wiki Activity
core-lightning/common/read_peer_msg.h

24 lines
695 B
C
Raw Normal View History

common: read_peer_msg helpers for per-peer subds. It's a bit ugly because each caller has slightly different needs, but we have three hooks and standard helpers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-31 13:23:35 +10:30
#ifndef LIGHTNING_COMMON_READ_PEER_MSG_H
#define LIGHTNING_COMMON_READ_PEER_MSG_H
#include "config.h"
#include <ccan/short_types/short_types.h>
#include <ccan/tal/tal.h>
struct crypto_state;
struct channel_id;
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-04 03:41:25 +09:30
struct per_peer_state;
common: read_peer_msg helpers for per-peer subds. It's a bit ugly because each caller has slightly different needs, but we have three hooks and standard helpers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-31 13:23:35 +10:30
common/read_peer_msg: deconstruct into individual helper routines. The One Big API is confusing, and has enough corner cases that we should ditch it rather than add more. See: https://www.sandimetz.com/blog/2016/1/20/the-wrong-abstraction In particular, when openingd is changed to chat to peers even when it's not actively opening a channel, it wants to handle (most) errors by continuing, not calling peer_failed(). This exposes the constituent parts. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-02 16:19:55 +09:30
/**
common: don't hang up when we receive a warning. We were allowed to, but the spec removed that. So we handle warnings differently from errors now. This also means the LND "internal error" workaround is done in lightningd (we still disconnect, but we don't want to close channel). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Changed: Protocol: we no longer disconnect every time we receive a warning message.
2023-09-12 13:53:14 +09:30
* handle_peer_error_or_warning - simple handler for errors / warnings
common/per_per_state: generalize lightningd/peer_comm Part 1 Encapsulating the peer state was a win for lightningd; not surprisingly, it's even more of a win for the other daemons, especially as we want to add a little gossip information. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-04 03:41:25 +09:30
* @pps: per-peer state.
common/read_peer_msg: fix header comment. Reported-by: @trueptolemy Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-05-09 09:28:54 +09:30
* @channel_id: the channel id of the current channel.
common/read_peer_msg: deconstruct into individual helper routines. The One Big API is confusing, and has enough corner cases that we should ditch it rather than add more. See: https://www.sandimetz.com/blog/2016/1/20/the-wrong-abstraction In particular, when openingd is changed to chat to peers even when it's not actively opening a channel, it wants to handle (most) errors by continuing, not calling peer_failed(). This exposes the constituent parts. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-02 16:19:55 +09:30
* @msg: the peer message (only taken if returns true).
*
common: don't hang up when we receive a warning. We were allowed to, but the spec removed that. So we handle warnings differently from errors now. This also means the LND "internal error" workaround is done in lightningd (we still disconnect, but we don't want to close channel). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Changed: Protocol: we no longer disconnect every time we receive a warning message.
2023-09-12 13:53:14 +09:30
* This returns true if it handled the packet (i.e. logs a warning).
* Doesn't return if it's an error.
common/gossip_store: handle timestamp filtering. This means we intercept the peer's gossip_timestamp_filter request in the per-peer subdaemon itself. The rest of the semantics are fairly simple however. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-04 03:49:25 +09:30
*/
common: don't hang up when we receive a warning. We were allowed to, but the spec removed that. So we handle warnings differently from errors now. This also means the LND "internal error" workaround is done in lightningd (we still disconnect, but we don't want to close channel). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Changed: Protocol: we no longer disconnect every time we receive a warning message.
2023-09-12 13:53:14 +09:30
bool handle_peer_error_or_warning(struct per_peer_state *pps,
const u8 *msg TAKES);
common/gossip_store: handle timestamp filtering. This means we intercept the peer's gossip_timestamp_filter request in the per-peer subdaemon itself. The rest of the semantics are fairly simple however. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-06-04 03:49:25 +09:30
common: read_peer_msg helpers for per-peer subds. It's a bit ugly because each caller has slightly different needs, but we have three hooks and standard helpers. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-01-31 13:23:35 +10:30
#endif /* LIGHTNING_COMMON_READ_PEER_MSG_H */
Reference in a new issue Copy permalink