a833fbe9b9
Motivation: Http2Stream has several methods that provide state information. We need to simplify how state is used and consolidate as many of these fields as possible. Modifications: Since we already have a concept of a stream being active or inactive, I'm now separating the deactivation of a stream from the act of closing it. The reason for this is the case of sending a frame with endOfStream=true. In this case we want to close the stream immediately in order to disallow further writing, but we don't want to mark the stream as inactive until the write has completed since the inactive event triggers the flow controller to cancel any pending writes on the stream. With deactivation separated out, we are able to eliminate most of the additional state methods with the exception of `isResetSent`. This is still required because we need to ignore inbound frames in this case (as per the spec), since the remote endpoint may not yet know that the stream has been closed. Result: Fixes #3382
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.