casper-network / casper-network/casper-node

Change networking to not deserialize incoming messages early

Open
#3,875 3 comments 0 reactions 1 assignee Claimed by @marc-casperlabs View on GitHub
Epic
Dominant language
Rust
Stars
399
Forks
224
Avg merge
15h 44m
Merged PRs (30d)
2

Description

The networking component should become completely agnostic of the actual component payload and only announce incoming bytes, along with a channel tag. Actual reading should be left to the components themselves.
Blocks: https://github.com/casper-network/casper-node/issues/3756 (this should replace the current block on that ticket)
Blocks: "Factor out additional networking logic from networking component"

this ticket really should be split into two parts: One is prepping the networking component to be able to support sending "raw" data, and the other one is actually moving the network message deserialization from raw into components. For comparison, currently data is encoded/decoded in the networking interface instead of individual components, except for consensus, which has a weird double serialization going on.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.