This repository has been archived by the owner on Sep 7, 2024. It is now read-only.
feat: adding response protocol #96
Closed
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
kehiy
added
core
0x9n0p
approved these changes
Dec 20, 2023
|
@0x9n0p is everything ok in this specification? |
|
@0x9n0p any updates on this? |
|
No. I'll work on it tomorrow. |
|
@0x9n0p Ok, waiting for your updates. ping me on telegram or discord for any help or question. lets finalise that! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Adding a protocol specification for better response sending. also, we can update our data type and accept
byteas the value of each element. for the last steps before implementation, we need to make sure it's compatible with TQL or maybe combine them into one thing to reduce complexity.Related Issue