Milestones
List view
- No due date•53/73 issues closed
- No due date•39/43 issues closed
- No due date•743/743 issues closed
This milestone includes general “tasks” which did not fit any other area but should be included anyway.
No due date•40/46 issues closedTLS related changes.
No due date•2/5 issues closedByteBuf is one of the most important parts of netty itself. We have a few changes in mind for it to make it more efficient and easier to maintain in the future.
No due date•35/36 issues closedFiles are currently not handled as good as buffers in terms of featureset. This milestone holds action items to address this.
No due date•0/2 issues closedHttp codec related changes that should be done as part of Netty 5.
No due date•13/18 issues closedhe ChannelHandler API remains mostly the same but there a few changes we would like to make. This milestone includes these.
No due date•12/13 issues closedThe Channel API represents the core abstract for transports. While the API did full-fill its job over the last years we found a few areas that should be improved. This milestone list the important ones we are aware of.
No due date•12/14 issues closedTopics related to ChannelPipeline API and sementics.
No due date•17/17 issues closedEventLoop serve as the core abstraction of event processing. This milestone list the proposed changes to the abstraction.
No due date•9/9 issues closedFutures and Promises are the core abstraction of asynchronous completation and notification. This milestone includes all the proposed related changes.
No due date•20/24 issues closed