History

Henry de Valence ed608f7231 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
..
src	Initial tower-based peer implementation. (#17 )	2019-10-07 15:36:16 -07:00
tests	Tracing endpoint (#3 )	2019-09-09 13:05:42 -07:00
Cargo.toml	Initial tower-based peer implementation. (#17 )	2019-10-07 15:36:16 -07:00
README.md	Create workspace skeleton based on design.md	2019-08-29 14:46:54 -07:00

README.md

Zebrad

Zebrad is an application.

Getting Started

This application is authored using Abscissa, a Rust application framework.

For more information, see: