-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Websocket should only call async_close once #4848
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should
do_close_
be reset tofalse
here? What ifon_write_fin
is called again?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, it doesn't look like it's needed since
write()
is not going to be called inon_write_fin()
ifdo_close_
is true andsend()
is not going to callwrite()
becauseclosing_
istrue
. Then I don't think two flags are needed. Can keepdo_close_
and have the check on line 264 and removedo_close_
on line 280. The check on line 264 prevents from initiatingasync_close
again inclose()
. Anddo_close_
set totrue
will allowasync_close
inon_write_fin()
if the queue was not empty whenclose()
was called.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great question. I don't think that setting
do_close_
tofalse
is a good idea, though. Then, ifwq_
is not empty we'd callon_write()
. We're trying to shut things down.If it's a problem that we need to address, and it feels like maybe it is, we could add yet another data member
bool closed_
and set ittrue
just as soon as we're inside this if. That would make thisif
look like...But I don't like the idea of adding yet another
bool
. Perhaps it would work better with anenum
for a state machine?Just a thought...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the feedback. Coincidentally, I had the realization about not needing
closing_
while having dinner, and came in to fix it before I even saw your comments. 😀