File tree Expand file tree Collapse file tree 1 file changed +0
-7
lines changed Expand file tree Collapse file tree 1 file changed +0
-7
lines changed Original file line number Diff line number Diff line change 4
4
//! Because we don't have a built-in runtime, it's up to the client to call events at a time in the
5
5
//! future, as well as generate and broadcast funding transactions handle payment preimages and a
6
6
//! few other things.
7
- //!
8
- //! Note that many events are handled for you by PeerHandler, so in the common design of having a
9
- //! PeerManager which marshalls messages to ChannelManager and Router you only need to call
10
- //! process_events on the PeerHandler and then get_and_clear_pending_events and handle the events
11
- //! that bubble up to the surface. If, however, you do not have a PeerHandler managing a
12
- //! ChannelManager you need to handle all of the events which may be generated.
13
- //TODO: We need better separation of event types ^
14
7
15
8
use ln:: msgs;
16
9
use ln:: channelmanager:: { PaymentPreimage , PaymentHash } ;
You can’t perform that action at this time.
0 commit comments