-
Notifications
You must be signed in to change notification settings - Fork 42
Removes async_append_some #283
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
Conversation
if (!on_push_) // Prepare for new message. | ||
on_push_ = is_next_push(); | ||
on_push_ = is_next_push(data); |
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.
This is likely not something to fix in this PR, but isn't the multiplexer violating point 1. in the comment above? While we're parsing something that's not a push and we run out of data, on_push_ will be false and we will look at the message's first byte even if we shouldn't.
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.
I have to review this again and test it. I remember it being trick see comments in is_next_push
.
df2036b
to
918889d
Compare
918889d
to
8ee2213
Compare
@anarthal I think I addressed all your comments. Your other PR will fix the remaining problems. |
Looks good to me. I'll merge mine after you merge this. |
@anarthal Before I start investigating how to proceed with @D0zee PR I would like to merge this one which simplifies how the read buffer is used.