Go to file
Norman Maurer ea94336689 DefaultChannelHandlerInvoker should work with non AbstractChannelHandlerContext sub-classes.
Motivation:

DefaultChannelHandlerInvoker currently blindly cast to AbstractChannelHandlerContext without checking if the ChannelHandlerContext is really a sub-type of it. It should check it first and if not just use slow-path implementation.

Modifications:

Do instanceof check first and if it fails just create a new Runnable instance of used the cached.

Result:

DefaultChannelHandlerInvoker works with any ChannelHandlerContext implementations.
2016-04-05 13:21:07 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
buffer Allow to disable leak detection for all buffers when using UnpooledByteBufAllocator. 2016-04-05 13:17:16 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-dns Remove an unused import 2016-04-02 01:39:47 -04:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-http [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
common [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
example [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
handler ApplicationProtocolNegotiationHandler doesn't work with SniHandler 2016-04-05 09:02:46 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
resolver [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport DefaultChannelHandlerInvoker should work with non AbstractChannelHandlerContext sub-classes. 2016-04-05 13:21:07 +02:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:36:54 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-04-02 01:25:05 -04:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +01:00
run-example.sh Map HTTP/2 Streams to Channels 2016-03-25 12:14:44 -07:00

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

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:

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

Development of all 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.