Only read one websocket frame at a time #27
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.
This PR reworks the websocket read logic to read exactly one websocket frame from the tcp buffer for each loop iteration. This is done by first peeking at the tcp buffer to read the header to read the payload size. The previous implementation just read the whole buffer, decoded the first websocket frame and discarded the remaining buffer. This leads to problems when there are multiple websocket frames already in the buffer.