bb6b251770
Motivation: We need to ensure we not swallow the close_notify that should be send back to the remote peer. See [#6167] Modifications: - Only call shutdown() in closeInbound() if there is nothing pending that should be send back to the remote peer. - Return the correct HandshakeStatus when the close_notify was received. - Only shutdown() when close_notify was received after closeOutbound() was called. Result: close_notify is correctly send back to the remote peer and handled when received.
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
Development of all 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.