Skip to content

Commit 53f5750

Browse files
committed
f - Clarify docs about PeerManager::process_events
1 parent 193f8c7 commit 53f5750

File tree

1 file changed

+3
-2
lines changed
  • lightning-background-processor/src

1 file changed

+3
-2
lines changed

lightning-background-processor/src/lib.rs

+3-2
Original file line numberDiff line numberDiff line change
@@ -29,14 +29,16 @@ use std::ops::Deref;
2929
/// `BackgroundProcessor` takes care of tasks that (1) need to happen periodically to keep
3030
/// Rust-Lightning running properly, and (2) either can or should be run in the background. Its
3131
/// responsibilities are:
32-
/// * Processing [`MessageSendEvent`]s by calling [`PeerManager::process_events`].
3332
/// * Processing [`Event`]s with a user-provided [`EventHandler`].
3433
/// * Monitoring whether the [`ChannelManager`] needs to be re-persisted to disk, and if so,
3534
/// writing it to disk/backups by invoking the callback given to it at startup.
3635
/// [`ChannelManager`] persistence should be done in the background.
3736
/// * Calling [`ChannelManager::timer_tick_occurred`] and [`PeerManager::timer_tick_occurred`]
3837
/// at the appropriate intervals.
3938
///
39+
/// It will also call [`PeerManager::process_events`] periodically though this shouldn't be relied
40+
/// upon as doing so may result in high latency.
41+
///
4042
/// # Note
4143
///
4244
/// If [`ChannelManager`] persistence fails and the persisted manager becomes out-of-date, then
@@ -46,7 +48,6 @@ use std::ops::Deref;
4648
///
4749
/// [`ChannelMonitor`]: lightning::chain::channelmonitor::ChannelMonitor
4850
/// [`Event`]: lightning::util::events::Event
49-
/// [`MessageSendEvent`]: lightning::util::events::MessageSendEvent
5051
#[must_use = "BackgroundProcessor will immediately stop on drop. It should be stored until shutdown."]
5152
pub struct BackgroundProcessor {
5253
stop_thread: Arc<AtomicBool>,

0 commit comments

Comments
 (0)