Complete message write to socket when socket cannot accept all bytes. #6
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
fwrite to a socket may not write all the requested bytes, so keep sending remaining bytes until done. Wait for the socket to be ready for writing between each attempt using the default send timeout value.
quipo
added a commit
that referenced
this pull request
Mar 7, 2014
Complete message write to socket when socket cannot accept all bytes.
|
thank you! |
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.
fwrite to a socket may not write all the requested bytes, so keep sending
remaining bytes until done. Wait for the socket to be ready for writing
between each attempt using the default send timeout value.
The library as it is currently written will fail if message sizes exceed the
allowed maximum SO_SNDBUF for the host system, or when there is
significant network congestion between the client and the server.
The fix has been used to consistently transfer 1 MBytes plus messages
across a North American transcontinental connection succesfully. Please
feel free to contact me if you need any more information! We really need
this fixed :)