Go to file
Norman Maurer 0d792c3aa0 Not trigger channelWritabilityChanged if fail messages before close Channel.
Motivation:

We should not trigger channelWritabilityChanged during failing message when we are about to close the Channel as otherwise the use may try again writing even if the Channel is about to get closed.

Modifications:

Add new boolean param to ChannelOutboundBuffer.failFlushed(...) which allows to specify if we should notify or not.

Result:

channelWritabilityChanged is not triggered anymore if we cloe the Channel because of an IOException during write.
2015-05-06 21:36:24 +02:00
all [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
buffer [#3623] CompositeByteBuf.iterator() should return optimized Iterable 2015-04-20 10:45:28 +02:00
codec Remove memory copy when extract frame in LengthFieldBasedFrameDecoder 2015-04-29 08:42:55 +02:00
codec-http Fix handling of non-auto read for ByteToMessageDecoder and SslHandler 2015-04-20 09:02:47 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
common fix a typo in RecyclableArrayList 2015-05-06 08:42:18 +02:00
example [#3531] Create SslContext.Builder 2015-04-14 07:27:55 +02:00
handler Only run OpenSslEngineTests if OpenSsl is installed. Related to [#3732] 2015-05-06 10:41:44 +02:00
license Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
testsuite Fix race-condition in SocketSslEchoTest 2015-05-06 06:25:15 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
transport Not trigger channelWritabilityChanged if fail messages before close Channel. 2015-05-06 21:36:24 +02:00
transport-native-epoll Fix regression introduced by 08e4b076be. 2015-05-06 17:56:45 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-31 22:06:30 -04:00
transport-sctp Add support for SCTP 'unordered' flag. 2015-04-30 08:06:53 +02:00
transport-udt Bugfix in channelUDT(). 2015-05-06 18:46:31 +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 Remove license of deque as we not use it anymore 2014-08-04 12:21:33 +02:00
pom.xml Add more profiles for newer JDK versions 2015-05-04 14:33:56 +09: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.