245fb52c90
Motivation: As described in #5734 Before this change, if the server had to do some sort of setup after a handshake was completed based on handshake's information, the only way available was to wait (in a separate thread) for the handshaker to be added as an attribute to the channel. Too much hassle. Modifications: Handshake completed event need to be stateful now, so I've added a tiny class holding just the HTTP upgrade request and the selected subprotocol which is fired as an event after the handshake has finished. I've also deprecated the old enum used as stateless event and I left the code that fires it for backward compatibility. It should be removed in the next mayor release. Result: It should be much simpler now to do initialization stuff based on subprotocol or request headers on handshake completion. No asynchronous waiting needed 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
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.