Go to file
Norman Maurer 26aa34853a Ensure correct ordering if a ChannelInitializer adds another ChannelInitializer
Motivation:

At the moment we call initChannel(...) in the channelRegistered(...) method which has the effect that if another ChannelInitializer is added within the initChannel(...) method the ordering of the added handlers is not correct and surprising. This is as the whole initChannel(...) method block is executed before the initChannel(...) block of the added ChannelInitializer is handled.

Modifications:

Call initChannel(...) from within handlerAdded(...) if the Channel is registered already. This is true in all cases for our DefaultChannelPipeline implementation. This way the ordering is always as expected. We still keep the old behaviour as well to not break code for other ChannelPipeline implementations (if someone ever wrote one).

Result:

Correct and expected ordering of ChannelHandlers.
2016-08-03 07:50:46 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
buffer Cleanup : removed unused empty arrays and simplified initialization 2016-08-02 07:03:59 +02:00
codec small performance fixes : unnecessary unboxing operations removed 2016-08-01 07:10:25 +02:00
codec-dns Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
codec-haproxy Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
codec-http Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
codec-stomp Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
common Cleanup : removed unused empty arrays and simplified initialization 2016-08-02 07:03:59 +02:00
example [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
handler Servers should not send duplicate intermediate certificates. 2016-08-01 10:52:46 +02:00
handler-proxy Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
license added support for Protobuf codec nano runtime 2016-01-19 21:39:17 +01:00
microbench retainSlice() unwrap ByteBuf 2016-07-29 11:16:44 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
resolver-dns Fix RejectedExecutionException when using DnsAddressResolverGroup 2016-08-01 10:21:10 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
transport Ensure correct ordering if a ChannelInitializer adds another ChannelInitializer 2016-08-03 07:50:46 +02:00
transport-native-epoll Removed custom split method as it is not effective anymore. 2016-08-01 21:49:33 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-07-27 13:29:56 +02:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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-07-27 13:29:56 +02: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 Add an example client for codec-redis 2016-04-23 11:18:12 -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.