Proper Message Serialization and Deserialization Using Individual Enums for Each Message #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add missed fields * Remove stream_bytes from GetFileResponse * Remove Option from peers_ipv6 * Change my field's type
…type i.e stream_file
|
Some fill-ups for Roadmap.
|
- Fixes requests without params eg: ping tests
- use message & address module from decent_protocol crate. - use Requestable interface from decentnet_protocol crate. - formatting changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proper Message Serialization and Deserialization Using Individual Enums for Each Message (5d0d09a) is main change introduced to the crate, all others are petty fixes and fill gaps for incomplete message templates.