ee3f3661f0
Motivation: See: https://github.com/netty/netty/issues/2402 See: https://tools.ietf.org/html/draft-ietf-httpbis-http2-10#section-3.5 Only the client should send the preface string, the server should not. "The server connection header consists of just a SETTINGS frame (Section 6.5) that MUST be the first frame the server sends in the HTTP/2 connection." Modifications: Split out Http2ClientPrefaceWriter and Http2ServerPrefaceReader from Http2FrameEncoder and Http2FrameDecoder. The new channel handlers are added to the pipeline and remove themselves after the preface is written/read. Result: HTTP2 client sends preface, server does not, in compliance with 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.