Related: e9685ea45aebcb4f9dad0f3a1fc328a06b4932dd Motivation: SslHandler.unwrap() does not evaluate the handshake status of SSLEngine.unwrap() when the status of SSLEngine.unwrap() is CLOSED. It is not correct because the status does not reflect the state of the handshake currently in progress, accoding to the API documentation of SSLEngineResult.Status. Also, sslCloseFuture can be notified earlier than handshake notification because we call sslCloseFuture.trySuccess() before evaluating handshake status. Modifications: - Notify sslCloseFuture after the unwrap loop is finished - Add more assertions to SocketSslEchoTest Result: Potentially fix the regression caused by: - e9685ea45aebcb4f9dad0f3a1fc328a06b4932dd
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.