298e7af647
Related: #3212 Motivation: When SslHandler and ChunkedWriteHandler exists in a pipeline together, it is possible that ChunkedWriteHandler.channelWritabilityChanged() invokes SslHandler.flush() and vice versa. Because they can feed each other (i.e. ChunkedWriteHandler.channelWritabilityChanged() -> SslHandler.flush() -> ChunkedWriteHandler.channelWritabilityChanged() -> ..), they can fall into an inconsistent state due to reentrance (e.g. bad MAC record at the remote peer due to incorrect ordering.) Modifications: - Trigger channelWritabilityChanged() using EventLoop.execute() when there's a chance where channelWritabilityChanged() can cause a reentrance issue - Fix test failures caused by the modification Result: Fix the handler reentrance issues related with a channelWritabilityChanged() event
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.