Go to file
Norman Maurer fe4a59011a
Do not schedule notify task if there are no listeners attached to the promise. (#8797)
Motivation:

If there are no listeners attached to the promise when full-filling it we do not need to schedule a task to notify.

Modifications:

- Don't schedule a task if there is nothing to notify.
- Add unit tests.

Result:

Fixes https://github.com/netty/netty/issues/8795.
2019-01-31 08:56:01 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn support publishing snapshots from docker based ci (#8634) 2018-12-07 05:43:06 +01:00
all [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
bom [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
buffer Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
codec Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-http Compare HttpMethod by reference (#8815) 2019-01-30 21:17:00 +01:00
codec-http2 Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
codec-xml Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
common Do not schedule notify task if there are no listeners attached to the promise. (#8797) 2019-01-31 08:56:01 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
docker Update to latest JDK8 and JDK11 releases (#8725) 2019-01-17 09:14:27 +01:00
example Compare HttpMethod by reference (#8815) 2019-01-30 21:17:00 +01:00
handler Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
handler-proxy Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
resolver [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite-autobahn Compare HttpMethod by reference (#8815) 2019-01-30 21:17:00 +01:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
testsuite-shading [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport Minimize memory footprint for AbstractChannelHandlerContext for handlers that execute in the EventExecutor. (#8786) 2019-01-28 19:45:38 +01:00
transport-native-epoll Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
transport-native-kqueue Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2019-01-21 12:26:44 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Exclude mainframer related files from git 2018-10-14 13:20:18 +02: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
mvnw Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
mvnw.cmd Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
NOTICE.txt Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
pom.xml Update to new checkstyle plugin (#8777) (#8780) 2019-01-25 11:58:42 +01:00
README.md Provide an Automatic-Module-Name for the netty-all artifact fixes #7644 2018-01-27 20:31:16 +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.all
  • 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.