4a45d23129
Motivation: There's no way for a user to get the encoder and the decoder of an HttpClientCodec. The lack of such getter methods makes it impossible to remove the codec handlers from the pipeline correctly. For example, a user could add more than one HttpClientCodec to the pipeline, and then the user cannot easily decide which encoder and decoder to remove. Modifications: - Add encoder() and decoder() method to HttpClientCodec which returns HttpRequestEncoder and HttpResponseDecoder respectively - Also made the same changes to HttpServerCodec Result: A user can distinguish the handlers added by multiple HttpClientCodecs easily.
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.