Go to file
Roger Kapsi 7460d90a67 Add listener to returned Future rather than passed in Promise
Motivation

It's cleaner to add listeners to returned Futures rather than provided Promises because the latter can have strange side effects in terms of listeners firing and called methods returning. Adding listeners preemtively may yield also to more OPS than necessary when there's an Exception in the to be called method.

Modifications

Add listener to returned ChannelFuture rather than given ChannelPromise

Result

Cleaner completion and exception handling
2017-06-16 13:21:19 +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 2017-06-08 21:06:24 +02:00
bom Add dependency management for missing entries 2017-06-14 20:26:33 +02:00
buffer [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-http Remove redundant code block in HttpPostRequestEncoder and make some cleanup 2017-06-14 06:49:20 +02:00
codec-http2 Use more aggressive expanding strategy in HpackHuffmanDecoder 2017-06-15 06:56:44 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-mqtt codec.mqtt: password and willMessage field types should be byte[] 2017-06-13 18:49:13 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
common Prevent unnecessary allocations in the StringUtil#escapeCsv 2017-06-13 14:57:38 -07:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
example [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
handler Add listener to returned Future rather than passed in Promise 2017-06-16 13:21:19 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02: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 Prevent unnecessary allocations in the StringUtil#escapeCsv 2017-06-13 14:57:38 -07:00
resolver [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
resolver-dns Let DnsNameResolver constructor use a default value for searchDomains 2017-06-13 15:43:08 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport Not fail the promise when a closed Channel is offered back to the ChannelPool 2017-06-13 18:50:20 +02:00
transport-native-epoll Add support for IP_TRANSPARENT socket option 2017-06-12 08:03:39 +02:00
transport-native-kqueue Not force to run autoconf and compile multiple times 2017-06-09 20:34:28 +02:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +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 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 2017-06-08 21:06:24 +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 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.