zecfoundation
/
zebra
mirror of https://github.com/ZcashFoundation/zebra.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zebra/zebra-network/src/peer.rs

19 lines
506 B
Rust
Raw Normal View History

Initial tower-based peer implementation. (#17) Add a tower-based peer implementation. Tower provides middleware for request-response oriented protocols, while Bitcoin/Zcash just send messages which could be interpreted either as requests or responses, depending on context. To bridge this mismatch we define our own internal request/response protocol, and implement a per-peer event loop that scans incoming messages and interprets them either as requests from the remote peer to our node, or as responses to requests we made previously. This is performed by the `PeerService` task, and a corresponding `PeerClient: tower::Service` can send it requests. These tasks are themselves created by a `PeerConnector: tower::Service` which dials a remote peer and performs a handshake.
2019-10-07 15:36:16 -07:00
//! Peer handling.
/// Handles outbound requests from our node to the network.
Beginning of peerset implementation. (#62) * Don't expose submodules of zebra_network::peer. * PeerSet, PeerDiscover stubs. Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> * Initial work on PeerSet. This is adapted from the MIT-licensed tower-balance implementation. * Use PeerSet in the connect stub.
2019-10-10 18:15:24 -07:00
mod client;
Add a PeerConnector wrapper around PeerHandshake
2019-10-22 12:44:08 -07:00
/// Wrapper around handshake logic that also opens a TCP connection.
mod connector;
Remove failure from zebra-chain, zebra-network. Failure uses a distinct Fail trait rather than the standard library's Error trait, which causes a lot of interoperability problems with tower and other Error-using crates. Since failure was created, the standard library's Error trait was improved, and its conveniences are now available without the custom Fail trait using `thiserror` (for easy error derives) and `anyhow` (for a better boxed Error).
2019-10-15 20:38:26 -07:00
/// Peer-related errors.
mod error;
Rename PeerConnector to PeerHandshake. It's only responsible for doing the handshakes, so it should be named that way, and then we can have a Connector responsible for actually opening the TCP connection.
2019-10-22 11:30:24 -07:00
/// Performs peer handshakes.
mod handshake;
Initial tower-based peer implementation. (#17) Add a tower-based peer implementation. Tower provides middleware for request-response oriented protocols, while Bitcoin/Zcash just send messages which could be interpreted either as requests or responses, depending on context. To bridge this mismatch we define our own internal request/response protocol, and implement a per-peer event loop that scans incoming messages and interprets them either as requests from the remote peer to our node, or as responses to requests we made previously. This is performed by the `PeerService` task, and a corresponding `PeerClient: tower::Service` can send it requests. These tasks are themselves created by a `PeerConnector: tower::Service` which dials a remote peer and performs a handshake.
2019-10-07 15:36:16 -07:00
/// Handles inbound requests from the network to our node.
Beginning of peerset implementation. (#62) * Don't expose submodules of zebra_network::peer. * PeerSet, PeerDiscover stubs. Co-authored-by: Deirdre Connolly <deirdre@zfnd.org> * Initial work on PeerSet. This is adapted from the MIT-licensed tower-balance implementation. * Use PeerSet in the connect stub.
2019-10-10 18:15:24 -07:00
mod server;
Rename `PeerClient` to `peer::Client`.
2019-11-27 11:27:17 -08:00
pub use client::Client;
Add a PeerConnector wrapper around PeerHandshake
2019-10-22 12:44:08 -07:00
pub use connector::PeerConnector;
Add a Mutex<HashSet<Nonce>> to detect self-conns.
2019-10-15 16:10:43 -07:00
pub use error::{HandshakeError, PeerError, SharedPeerError};
Rename PeerConnector to PeerHandshake. It's only responsible for doing the handshakes, so it should be named that way, and then we can have a Connector responsible for actually opening the TCP connection.
2019-10-22 11:30:24 -07:00
pub use handshake::PeerHandshake;
Rename PeerServer -> peer::Server
2019-11-27 11:31:35 -08:00
pub use server::Server;