Move syncing code from `sc-network-common` to `sc-network-sync` (#1912)
This PR moves syncing-related code from `sc-network-common` to `sc-network-sync`. Unfortunately, some parts are tightly integrated with networking, so they were left in `sc-network-common` for now: 1. `SyncMode` in `common/src/sync.rs` (used in `NetworkConfiguration`). 2. `BlockAnnouncesHandshake`, `BlockRequest`, `BlockResponse`, etc. in `common/src/sync/message.rs` (used in `src/protocol.rs` and `src/protocol/message.rs`). More substantial refactoring is needed to decouple syncing and networking completely, including getting rid of the hardcoded sync protocol. ## Release notes Move syncing-related code from `sc-network-common` to `sc-network-sync`. Delete `ChainSync` trait as it's never used (the only implementation is accessed directly from `SyncingEngine` and exposes a lot of public methods that are not part of the trait). Some new trait(s) for syncing will likely be introduced as part of Sync 2.0 refactoring to represent syncing strategies.
Showing
- Cargo.lock 5 additions, 0 deletionsCargo.lock
- substrate/client/consensus/grandpa/Cargo.toml 1 addition, 0 deletionssubstrate/client/consensus/grandpa/Cargo.toml
- substrate/client/consensus/grandpa/src/communication/mod.rs 1 addition, 1 deletionsubstrate/client/consensus/grandpa/src/communication/mod.rs
- substrate/client/consensus/grandpa/src/communication/tests.rs 2 additions, 4 deletions...trate/client/consensus/grandpa/src/communication/tests.rs
- substrate/client/consensus/grandpa/src/warp_proof.rs 1 addition, 1 deletionsubstrate/client/consensus/grandpa/src/warp_proof.rs
- substrate/client/informant/Cargo.toml 1 addition, 0 deletionssubstrate/client/informant/Cargo.toml
- substrate/client/informant/src/display.rs 1 addition, 1 deletionsubstrate/client/informant/src/display.rs
- substrate/client/informant/src/lib.rs 1 addition, 1 deletionsubstrate/client/informant/src/lib.rs
- substrate/client/network-gossip/Cargo.toml 1 addition, 0 deletionssubstrate/client/network-gossip/Cargo.toml
- substrate/client/network-gossip/src/bridge.rs 3 additions, 2 deletionssubstrate/client/network-gossip/src/bridge.rs
- substrate/client/network-gossip/src/lib.rs 1 addition, 1 deletionsubstrate/client/network-gossip/src/lib.rs
- substrate/client/network/common/src/sync.rs 0 additions, 342 deletionssubstrate/client/network/common/src/sync.rs
- substrate/client/network/common/src/sync/warp.rs 0 additions, 101 deletionssubstrate/client/network/common/src/sync/warp.rs
- substrate/client/network/src/config.rs 7 additions, 7 deletionssubstrate/client/network/src/config.rs
- substrate/client/network/src/lib.rs 1 addition, 8 deletionssubstrate/client/network/src/lib.rs
- substrate/client/network/statement/Cargo.toml 1 addition, 0 deletionssubstrate/client/network/statement/Cargo.toml
- substrate/client/network/statement/src/lib.rs 2 additions, 4 deletionssubstrate/client/network/statement/src/lib.rs
- substrate/client/network/sync/src/block_request_handler.rs 3 additions, 1 deletionsubstrate/client/network/sync/src/block_request_handler.rs
- substrate/client/network/sync/src/chain_sync.rs 2435 additions, 0 deletionssubstrate/client/network/sync/src/chain_sync.rs
- substrate/client/network/sync/src/chain_sync/test.rs 1085 additions, 0 deletionssubstrate/client/network/sync/src/chain_sync/test.rs
Please register or sign in to comment