auto grows the buffer to workaround the lack of fragmentation support #782
Conversation
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
|
Merged. |
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.
To workaround this issue: #401
And the following related issues:
According to https://bugs.chromium.org/p/chromium/issues/detail?id=1069431, it looks like that we won't get fragmentation support in the near future. Meanwhile, the underlying package https://github.com/gobwas/ws adds auto growing feature recently, so that we can address the issue from the client side.
Please note that this PR is not ready for merged yet, because it uses the new feature in the RC version, and the new feature has some issues (see gobwas/ws#134).