From: bmancini55 Date: Tue, 15 Dec 2020 18:48:14 +0000 (-0500) Subject: Fix comment for sync_routing_table X-Git-Tag: v0.0.13~50^2 X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=c026764e8d818a719d40aafd3d6580cac1e47c45;p=rust-lightning Fix comment for sync_routing_table Corrects the comment for sync_routing_table in RoutingMessageHandler to be less prescriptive about the implementor's actions. --- diff --git a/lightning/src/ln/msgs.rs b/lightning/src/ln/msgs.rs index b392a22ed..25553c708 100644 --- a/lightning/src/ln/msgs.rs +++ b/lightning/src/ln/msgs.rs @@ -831,9 +831,9 @@ pub trait RoutingMessageHandler : Send + Sync + events::MessageSendEventsProvide /// immediately higher (as defined by ::cmp) than starting_point. /// If None is provided for starting_point, we start at the first node. fn get_next_node_announcements(&self, starting_point: Option<&PublicKey>, batch_amount: u8) -> Vec; - /// Initiates routing gossip sync by querying a peer to discover channels - /// and their associated routing gossip messages. This method will use a - /// sync strategy defined by the implementor. + /// Called when a connection is established with a peer. This can be used to + /// perform routing table synchronization using a strategy defined by the + /// implementor. fn sync_routing_table(&self, their_node_id: &PublicKey, init: &Init); /// Handles the reply of a query we initiated to learn about channels /// for a given range of blocks. We can expect to receive one or more