Multi-packet responses #24
Open
Conversation
This file contains hidden or 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
|
@thedudeguy Merge? |
piotrskibapl
force-pushed
the
multi-packet-responses
branch
from
3cf0fcc to
f89720e
Compare
piotrskibapl
force-pushed
the
multi-packet-responses
branch
from
f89720e to
bbe6760
Compare
|
@SomKen it looks like the author is not active on GitHub, but if you still use this code, I just updated the pull request with some improvements. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Reading responses bigger than 4096 was not possible due to splitting the response into multiple packets. I've addressed the issue by sending additional "ping" command packet and looking for "Pong!" response which should be right after the expected response.