refactor(SocketLayer)!: moving MaxPacketSize to SocketFactory #1056
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
James-Frowen
changed the title
James-Frowen
changed the title
Allows max packet size to be set by sockets rather than the general peer config. BREAKING CHANGE: socket factories now have to override MaxPacketSize property
James-Frowen
force-pushed
the
max-packet-size
branch
from
7ed8a7b
to
ec91dd3
Compare
|
Kudos, SonarCloud Quality Gate passed! |
|
🎉 This PR is included in version 120.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Allows max packet size to be set by sockets rather than the general peer config.
BREAKING CHANGE: socket factories not have to override abstract MaxPacketSize property