0b12592acb
Motivation: Slicing a mutable CompositeByteBuf is not the appropriate mechanism to use to track and release buffers that have been written to a channel. In particular buffers passed over an Embedded or LocalChannel are retained after the ChannelPromise is completed and listening to the promise to consolidate a CompositeBuffer breaks slices taken from the composite as the offset indices have changed. In addition CoalescingBufferQueue handles taking arbitrarily sized slices of a sequence of buffers more efficiently. Modifications: Convert FlowControlledData to use a CoalescingBufferQueue to handle merging data writes. Result: HTTP2 works over LocalChannel and code is considerably simpler.
Netty Project
Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.
Links
How to build
For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.
You require the following to build Netty:
- Latest stable Oracle JDK 7
- Latest stable Apache Maven
- If you are on Linux, you need additional development packages installed on your system, because you'll build the native transport.
Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.
Branches to look
The 'master' branch is where the development of the latest major version lives on. The development of all other versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.