Go to file
Norman Maurer 253cd694ef Ensure we not leave data in the BIO when error happens.
Motivation:

We need to ensure we consume all pending data in the BIO on error to correctly send the close notify for the remote peer.

Modifications:

Correctly force the user to call wrap(...) if there is something left in the BIO.

Result:

close_notify is not lost.
2015-12-17 12:40:19 +09:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer Move Hex dump related util from ByteBufUtil to inner class 2015-12-11 19:47:57 +01:00
codec Use ByteBuf.*LE methods for write and read LE 2015-12-10 09:34:27 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-http [#4505] Correctly handle whitespaces in websocket uri's. 2015-12-10 13:52:42 +01:00
codec-http2 Allow to set Http2HeaderEncoder.SensitivityDetector in the Http2ConnectionHandler 2015-12-10 14:34:04 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
codec-xml [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
common Moving KObjectHashMapTest to propert directory 2015-12-14 10:08:41 -08:00
example [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
handler Ensure we not leave data in the BIO when error happens. 2015-12-17 12:40:19 +09:00
handler-proxy Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
license [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
microbench DefaultChannelConfig maxMessagesPerRead default not always set 2015-11-25 15:14:07 -08:00
resolver Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
resolver-dns Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
transport Extract SocketAdress logic from NameResolver 2015-12-14 14:03:50 +01:00
transport-native-epoll [#4449] Remove registered events from eventloop before close 2015-12-13 09:55:50 +01:00
transport-rxtx Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
transport-sctp Use OneTimeTask where possible to reduce object creation 2015-11-20 14:39:06 -08:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +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:36:54 +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:13:58 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt [#4331] Helper methods to get charset from Content-Type header of HttpMessage 2015-11-19 15:59:34 -08:00
pom.xml update pom due to alpn provided 2015-11-23 12:52:51 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:59:11 +01:00
run-example.sh Add HTTP/2 Netty tiles example 2015-05-18 14:16:54 -07: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 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.