1429543436
Motivation: Currently, Http2LifecycleManager implements the exception handling logic which makes it difficult to extend or modify the exception handling behavior. Simply overriding exceptionCaught() will only affect one of the many possible exception paths. We need to reorganize the exception handling code to centralize the exception handling logic into a single place that can easily be extended by subclasses of Http2ConnectionHandler. Modifications: Made Http2LifecycleManager an interface, implemented directly by Http2ConnectionHandler. This adds a circular dependency between the handler and the encoder/decoder, so I added builders for them that allow the constructor of Http2ConnectionHandler to set itself as the lifecycle manager and build them. Changed Http2LifecycleManager.onHttpException to just onException(Throwable) to simplify the interface. This method is now the central control point for all exceptions. Subclasses now only need to override onException() to intercept any exception encountered by the handler. Result: HTTP/2 has more extensible exception handling, that is less likely to see exceptions vanish into the ether. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-dns | ||
| codec-haproxy | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-mqtt | ||
| codec-socks | ||
| codec-stomp | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| 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.