034e0bd8d2
Motivation: With the current implementation the client protocol preference list takes precedence over the one of the server, since the select method will return the first item, in the client list, that matches any of the protocols supported by the server. This violates the recommendation of http://tools.ietf.org/html/rfc7301#section-3.2. It will also fail with the current implementation of Chrome, which sends back Extension application_layer_protocol_negotiation, protocols: [http/1.1, spdy/3.1, h2-14] Modifications: Changed the protocol negotiator to prefer server’s list. Added a test case that demonstrates the issue and that is fixed with the modifications of this commit. Result: Server’s preference list is used.
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 major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.