should update interest after process_send immediately #364
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
|
I update my patch , make it more clearly . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
some tcp server can't work with gnirehtet well .
old code work in this way:
In this situation :
relay-rust call process() first , and both ready.is_readable() and ready.is_writable() are true .
relay-rust do process_send() successfully , and then call process_receive()? ( ? is important )
process_receive()? throw error(would block) to on_ready() , on_ready() will ignore this err_wouldblock .
BECAUSE process_receive throw error ,so self.update_interests(selector) in process() won't be called .
Ant the next process() will still be interest with read and write .
but the write buff is null ,so the connection is closed .