b7aef7bec8
Motivation: Other implementations of FullHttpMessage allow .toString to be called after the Message has been released This brings AggregatedFullHttpMessage into line with those impls. Modifications: - Changed AggregatedFullHttpMessage to no longer be a sub-class of DefaultByteBufHolder - Changes AggregatedFullHttpMessage to implement ByteBufHolder - Hold the content buffer internally to AggregatedFullHttpMessage - Implement the required content() and release() methods that were missing - Do not check refcnt when accessing content() (similar to DefaultFullHttpMessage) Result: A released AggregatedFullHttpMessage can have .toString called without throwing an exception
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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.