Go to file
Tibor Csögör 9d4fae308c ChannelInitializer: change propagation of channelRegistered event
Motivation:

If a handler is added to the pipeline within ChannelInitializer::initChannel via
addFirst(...) then it will not receive the channelRegistered event.  The same
handler added via addLast(...) will receive the event.  This different behavior
is unlikely to be expected by users and can cause confusion.

Modifications:

Let ChannelInitializer::channelRegistered propagate the event by passing it to
the pipeline instead of firing it on the ChannelHandlerContext.

Result:

The channelRegistered event is propagated to handlers regardless of the method
used to add it to the pipeline (addFirst/addLast).
2016-03-31 09:01:00 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-http [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-http2 [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
common Allow to customize NIO (channel) select strategies. 2016-03-30 15:01:25 -07:00
example [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
handler [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02: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-03-29 16:45:13 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
transport ChannelInitializer: change propagation of channelRegistered event 2016-03-31 09:01:00 +02:00
transport-native-epoll EPOLL SelectStrategy 2016-03-30 15:11:35 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-03-29 16:45:13 +02: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-03-29 16:45:13 +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 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.