d35ddf0648
Motivation: Outbound flow control does not properly remove the head of queue after it's written. This will cause streams with multiple frames to get stuck and not send all of the data. Modifications: Modified the DefaultHttp2OutboundFlowController to properly remove the head of the pending write queue once a queued frame has been written. Added an integration test that sends a large message to verify that all DATA frames are properly collected at the other end. Result: Outbound flow control properly handles several queued messages.
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.