Go to file
Scott Mitchell 2d815fa752 DefaultChannelPipeline will not invoke handler if events are fired from handlerAdded
Motiviation:
DefaultChannelPipeline and AbstractChannelHandlerContext maintain state
which indicates if a ChannelHandler should be invoked or not. However
the state is updated to allow the handler to be invoked only after the
handlerAdded method completes. If the handlerAdded method generates
events which may result in other methods being invoked on that handler
they will be missed.

Modifications:
- DefaultChannelPipeline should set the state before calling
handlerAdded

Result:
DefaultChannelPipeline will allow events to be processed during the
handlerAdded process.
2018-01-24 10:32:48 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
buffer Fix ByteBuf.nioBuffer(...) and nioBuffers(...) docs to reflect reality. 2018-01-22 19:50:08 +01:00
codec Use FastThreadLocal for CodecOutputList 2018-01-23 11:34:28 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-http [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-http2 Http2FrameCodec WindowUpdate bug 2018-01-22 11:17:56 -08:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
codec-stomp Reduce memory allocations in StompSubframeDecoder.readHeaders 2018-01-23 15:27:57 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
common [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
docker Provide a Docker image for reproducible builds 2018-01-22 20:02:17 +01:00
example [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
handler [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Use FastThreadLocal for CodecOutputList 2018-01-23 11:34:28 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
resolver-dns Fix race-condition when using DnsCache in DnsNameResolver 2018-01-23 08:04:33 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport DefaultChannelPipeline will not invoke handler if events are fired from handlerAdded 2018-01-24 10:32:48 +01:00
transport-native-epoll [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00: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 Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2018-01-21 12:53:51 +00:00
README.md Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.