Comments (1)
Seems to be fairly feasible with a small bit of cleanup, especially for components like the fetcher. Backpressure propagation would be as follows:
- Upstream components (mainly the synchronizer) will be asked to have a defined limit on the number of parallel requests they make. They need not worry about timeouts, since the fetcher can now guarantee a response (albeit an error one).
- Fetcher itself knows the capacity of each peer (via chainspec configuration and can balance accordingly), keeping an internal, unlimited queue (which is low on memory usage, since it only stores IDs).
- Networking does no longer buffer any message beyond the buffers built into the transport itself (
juliet
). - Proper request-response handling is used (see sample code), resulting in
.respond()
to be called to answer requests coming, and requests being made are made solely throughEffectBuilder::make_network_request
.
Essentially this results in a respnse or error being associated with every request made, all enforced by the networking layer. Fetcher and higher up components need not concern themselves with these.
See the 4561-request-response-eval
branch for some sample code.
from casper-node.
Related Issues (20)
- Error encountered while running a freshly compiled NCTL network from feat-2.0.
- Rust toolchain failure observed with CEP18 contract.
- Fix Juliet test HOT 1
- Add a flag for enabling speculative exec into the binary port and disable it by default
- Add a dictionary item request to the binary port
- Move ReactorState from casper-types to the node and replace it with a String in NodeStatus
- Rename Transform types
- Review max_request_size_bytes and max_response_size_bytes binary port config
- Send custom error message payloads in the binary port
- Investigate potentially flaky Highway Zug rewards tests
- Joiner issue for 1.6 HOT 1
- Wrong documentation for enable_contract_version
- Distributing rewards for signatures sometimes fail if the validator dropped from the validator list
- BlockValidator can sometimes drop responders without responding HOT 1
- Create a reactor test that checks that new 2.0 rewards are correctly distributed to inactive validators
- Move values that can affect size of the BinaryPort request to chainspec
- Create a tool for direct communication with binary port
- Adjust cost values for contract messages FFI parameters
- Write reactor tests for checking transaction payments HOT 1
- Unintended speed dependence in should_have_diverse_proposable_blocks_with_stocked_buffer test
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from casper-node.