f325c261cc
Motivation: There's no way to generate the name of a handler being newly added automatically and reliably. For example, let's say you have a routine that adds a set of handlers to a pipeline using addBefore() or addAfter(). Because addBefore() and addAfter() always require non-conflicting non-null handler name, making the multiple invocation of the routine on the same pipeline is non-trivial. Modifications: - If a user specifies null as the name of the new handler, DefaultChannelPipeline generates one. - Update the documentation of ChannelPipeline to match the new behavior Result: A user doesn't need to worry about name conflicts anymore.
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.