A small change to the API of the connection scheduler.
Instead of having to call ConnectionScheduler::new() with a Vec of (PublicKey, String), peers can now be added and removed via the new add_peer and remove_peer methods after the default instance of the connection scheduler has been created. This has the advantage of allowing peers to be added and removed from the scheduler throughout the node's operation (for example, through messages sent via the broker and acted upon in the message loop of the scheduler).
A small change to the API of the connection scheduler.
Instead of having to call
ConnectionScheduler::new()with aVecof(PublicKey, String), peers can now be added and removed via the newadd_peerandremove_peermethods after the default instance of the connection scheduler has been created. This has the advantage of allowing peers to be added and removed from the scheduler throughout the node's operation (for example, through messages sent via the broker and acted upon in the message loop of the scheduler).