700ac93b15
Currently the DefaultHttp2InboundFlowController only supports the ability to turn on and off "window maintenance" for a stream. This is insufficient for true application-level flow control that may only want to return a few bytes to flow control at a time. Modifications: Removing "window maintenance" interface from DefaultHttp2InboundFlowController in favor of the new interface. Created the Http2InboundFlowState interface which extends Http2FlowState to add the ability to return bytes for a specific stream. Changed the onDataRead method to return an integer number of bytes that will be immediately returned to flow control, to support use cases that want to opt-out of application-level inbound flow control. Updated DefaultHttp2InboundFlowController to use 2 windows per stream. The first, "window", is the actual flow control window that is decremented as soon as data is received. The second "processedWindow" is a delayed view of "window" that is only decremented after the application returns the processed bytes. It is processedWindow that is used when determining when to send a WINDOW_UPDATE to restore part of the inbound flow control window for the stream/connection. Result: The HTTP/2 inbound flow control interfaces support application-level flow control. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-dns | ||
| codec-haproxy | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-mqtt | ||
| codec-socks | ||
| codec-stomp | ||
| common | ||
| example | ||
| handler | ||
| handler-proxy | ||
| license | ||
| microbench | ||
| resolver | ||
| resolver-dns | ||
| tarball | ||
| testsuite | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbprefs | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| LICENSE.txt | ||
| NOTICE.txt | ||
| pom.xml | ||
| README.md | ||
| run-example.sh | ||
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.