Move requests-responses and polling from `ChainSync` to `SyncingEngine` (#1650)
Move request-response handling from `ChainSync` to `SyncingEngine` as part of [Sync 2.0](https://github.com/paritytech/polkadot-sdk/issues/534) refactoring aimed at making `ChainSync` a pure state machine. Resolves https://github.com/paritytech/polkadot-sdk/issues/502. --------- Co-authored-by:Aaro Altonen <48052676+altonen@users.noreply.github.com> Co-authored-by:
Bastian Köcher <git@kchr.de>
Showing
- Cargo.lock 1 addition, 0 deletionsCargo.lock
- substrate/client/network/common/src/sync.rs 18 additions, 10 deletionssubstrate/client/network/common/src/sync.rs
- substrate/client/network/sync/Cargo.toml 1 addition, 0 deletionssubstrate/client/network/sync/Cargo.toml
- substrate/client/network/sync/src/engine.rs 360 additions, 22 deletionssubstrate/client/network/sync/src/engine.rs
- substrate/client/network/sync/src/lib.rs 113 additions, 499 deletionssubstrate/client/network/sync/src/lib.rs
- substrate/client/network/sync/src/mock.rs 1 addition, 11 deletionssubstrate/client/network/sync/src/mock.rs
- substrate/client/network/sync/src/pending_responses.rs 114 additions, 0 deletionssubstrate/client/network/sync/src/pending_responses.rs
- substrate/client/rpc-spec-v2/Cargo.toml 1 addition, 1 deletionsubstrate/client/rpc-spec-v2/Cargo.toml
Please register or sign in to comment