Go to file
Scott Mitchell e3f1416478 LocalChannelWrite event sequencing issue
Motivation:
https://github.com/netty/netty/pull/4143 addressed a few ordering issues but an ordering issue still remained if the Promise for a write completes, and a listener of that promise does a write on a peer channel. The ordering was subject to how potentially 2 different executors would run a task, but it should be coordinated such that the first write is read first.

Modifications:
- Keep track of the finishPeerRead task run on the executor if necessary and ensure it completes before current channel read occurs

Result:
Ordering of events for echo type situations is preserved.
2015-08-28 11:28:55 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
buffer Restore derived buffer index/mark updates 2015-08-27 10:24:48 -07:00
codec [#4087] Correctly forward bytes when remove codec and handle channelInactive / channelReadComplete(...) 2015-08-21 18:26:05 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
codec-http [#4079] Fix IllegalStateException when HttpContentEncoder is used and 100 Continue response is used. 2015-08-21 07:53:45 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
common Allow to get details of the Thread that powers a SingleThreadEventExecutor. 2015-08-28 15:33:51 +02:00
example [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
handler Backport ipfilter handler 2015-08-21 08:10:14 +02:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench Microbench backport issue 2015-07-30 10:33:10 -07:00
tarball [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
testsuite Allow to create SslContext from existing PrivateKey / X509Certificate 2015-08-12 14:59:48 +02:00
testsuite-osgi Add a property to disable osgi testsuite run 2015-08-13 09:53:55 +09:00
transport LocalChannelWrite event sequencing issue 2015-08-28 11:28:55 -07:00
transport-native-epoll Only try to obtain SO_LINGER on close if fd is still open. 2015-08-28 14:50:00 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +02:00
transport-sctp OioSctpChannel iterating over selected keys 2015-08-27 10:19:29 -07:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-07-24 10:11:44 +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: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 Build fails with java 1.8_u60 2015-08-28 08:57:10 -07:00
README.md Add a link to the 'native transports' page 2014-07-21 12:54:43 -07: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

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.