bcb180b08d
Motivation: The connection, priority tree, and inbound/outbound flow controllers each maintain a separate map for stream information. This is wasteful and complicates the design since as streams are added/removed, multiple structures have to be updated. Modifications: - Merging the priority tree into Http2Connection. Then we can use Http2Connection as the central stream repository. - Adding observer pattern to Http2Connection so flow controllers can be told when a new stream is created, closed, etc. - Adding properties for inboundFlow/outboundFlow state to Http2Stream. This allows the controller to access flow control state directly from the stream without requiring additional structures. - Separate out the StreamRemovalPolicy and created a "default" implementation that runs periodic garbage collection. This used to be internal to the outbound flow controller, but I think it is more general than that. Result: HTTP/2 classes will require less storage for new streams.
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.