Go to file
Trustin Lee 28caa873b3 Don't trigger IOException at ChunkedStream.isEndOfInput()
Related: #3368

Motivation:

ChunkedWriteHandler checks if the return value of
ChunkedInput.isEndOfInput() after calling ChunkedInput.close().

This makes ChunkedStream.isEndOfInput() trigger an IOException, which is
originally triggered by PushBackInputStream.read().

By contract, ChunkedInput.isEndOfInput() should not raise an IOException
even when the underlying stream is closed.

Modifications:

Add a boolean flag that keeps track of whether the underlying stream has
been closed or not, so that ChunkedStream.isEndOfInput() does not
propagate the IOException from PushBackInputStream.

Result:

Fixes #3368
2015-03-31 11:31:54 +09:00
all [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
buffer Updates the javadoc of Unpooled to remove mention to methods it does not provide 2015-03-04 12:03:50 +09:00
codec Add support for byte order to LengthFieldPrepender 2015-03-13 19:30:49 +01:00
codec-http Fix example in CookieDecoder Javadoc 2015-03-26 11:49:30 +09:00
codec-socks Hide password in exception messages of SocksAuthRequest 2015-03-17 17:23:30 +09:00
common Respect -Djava.net.preferIPv4Stack when using epoll transport 2015-03-11 02:49:33 +01:00
example [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
handler Don't trigger IOException at ChunkedStream.isEndOfInput() 2015-03-31 11:31:54 +09: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-02 01:31:30 -05:00
tarball [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport Small typos fixes in Channel's Javadoc 2015-03-21 16:13:05 +01:00
transport-native-epoll First load RuntimeException to prevent segfault on error 2015-03-13 18:28:32 +01:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-03-02 01:31:30 -05: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 supported for X509ExtendedTrustManager when using OpenSslEngine 2015-03-30 09:05:09 +02: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.