Bump to Netty 4.2.0 #1380
Draft
Bump to Netty 4.2.0 #1380
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
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.
This is the upcoming release of Netty. Unlike prior attempts (cough Netty 5 cough), this time around, there will probably be a final release (and there's been 100+ "patch" releases of 4.1, so a version bump is well overdue!)
The main architectural change is that I/O transports are decoupled from the event loop group implementation. The other major feature is support for the
io_uringtransport, which is going to become stable in Netty 4.2, so let's add support for it officially in Velocity. The new transport should be much more efficient than the existing epoll one for Linux users, and will support many more players on a given proxy.