00853d9453
Motivation: In the early days of 5.0, we merged ChannelInboundHandler and ChannelOutboundHandler into ChannelHandler, and introduced the annotation called 'Skip'. The annotation 'Skip' was introduced to determine which handler methods are no-op (i.e. simply forwarding the event to the next handler) so that DefaultChannelHandlerContext doesn't even need to submit an event-invoking task to an EventExecutor, significantly reducing the context switches. However, this introduced a regression for the handlers which implemented write() but not flush(). Because flush() was skippable for such handlers, flush() event went through to the next handler before write() does. To address this problem, we came up with a naive workaround that sets MASK_FLUSH when MASK_WRITE is set. Although the previous workaround works fine for many cases, we still seem to have an event ordering problem. We keep seeing the intermittant failure of LocalTransportThreadModelTest.testStagedExecution(), because other handler methods are still skipped. Modifications: We do not skip the execution of handler methods annotated with 'Skip' unless all inbound methods (or all outbound methods) are marked with 'Skip'. Result: This change Brings back the event ordering behavior of 4.x, making LocalTransportThreadModelTest.testStagedExecution() pass. |
||
|---|---|---|
| all | ||
| buffer | ||
| codec | ||
| codec-http | ||
| codec-http2 | ||
| codec-memcache | ||
| codec-socks | ||
| common | ||
| example | ||
| handler | ||
| license | ||
| microbench | ||
| tarball | ||
| testsuite | ||
| transport | ||
| transport-native-epoll | ||
| transport-rxtx | ||
| transport-sctp | ||
| transport-udt | ||
| .fbfilter.xml | ||
| .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
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.