Go to file
Norman Maurer 6a4a9f7493 Correctly run pending tasks before flush and also remove incorrect assert.
Motivation:

We need to ensure we run all pending tasks before doing any flush in writeOutbound(...) to ensure all pending tasks are run first. Also we should remove the assert of the future and just add a listener to it so it is processed later if needed. This is true as a user may schedule a write for later execution.

Modifications:

- Remove assert of future in writeOutbound(...)
- Correctly run pending tasks before doing the flush and also before doing the close of the channel.
- Add unit tests to proof the defect is fixed.

Result:

Correclty handle the situation of delayed writes.
2016-03-29 14:30:47 +02:00
all [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
buffer Fix setBytes when source is read-only ByteBuffer and target is pooled buffer 2016-03-22 09:19:39 +01:00
codec [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
codec-http Backport InternalThreadLocalMap reusable ArrayList 2016-03-23 17:29:00 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
common Backport InternalThreadLocalMap reusable ArrayList 2016-03-23 17:29:00 +01:00
example [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
handler Read if needed on NEED_UNWRAP 2016-03-29 08:48:08 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Speed up the slow path of FastThreadLocal 2016-03-23 11:44:30 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
transport Correctly run pending tasks before flush and also remove incorrect assert. 2016-03-29 14:30:47 +02:00
transport-native-epoll Not attempt to read from fd when channel is closed during read loop. Related to [#5031] 2016-03-29 10:56:54 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-03-21 10:34:26 +01: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:37:12 +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:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Upgrade netty-tcnative to 1.1.33.Fork15 2016-03-23 11:46:05 +01:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +09: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.