Motivation: A few items were identified where the http2 codec is out of compliance with the spec. Modifications: - Fixed handling of priority weight on the wire. Now adding 1 after reading from the wire and subtracing 1 before writing. - Fixed handling of next stream ID. Client streamIds were starting at 3, but they need to start at 1 to allow the upgrade from HTTP/1.1. Also making next stream ID logic more flexible. Allowing the next created stream to be any number in the sequence following the previously created stream. - Disallowing SETTINGS frames with ENABLE_PUSH specified for server endpoints. This means that attempts to write this frame from a server, or read it from a client will fail. Result: The http2 implementation will be more inline with the spec.
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
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.