Go to file
Norman Maurer b91c9be878 Correctly set the alert type depending of the CertificateException
Motivation:

Depending on the actual CertificateException we should set the correct alert type so it will be sent back to the remote peer and so make it easier for them to fix it.

Modification:

Correctly set the alert and not always just use a general alert.

Result:

It's easier for the remote peer to fix the problems.
2016-02-19 08:28:55 -08:00
all [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
buffer ByteBufUtil.writeUtf8 not consistent with String.getBytes(Charset) 2016-02-11 08:27:22 -08:00
codec Ensure read components can be discarded when COMPOSITE_CUMULATOR is used. 2016-02-17 19:51:29 -08:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
codec-http ByteToMessageDecoder ChannelInputShutdownEvent support 2016-02-12 16:29:00 -08:00
codec-socks [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
common Leak Detector disclosing when records dropped 2016-02-12 09:58:10 -08:00
example Allow to specify tcnative artifactId and verion to allow run tests easily with different tcnative flavors 2016-01-29 22:25:03 +01:00
handler Correctly set the alert type depending of the CertificateException 2016-02-19 08:28:55 -08:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
testsuite Upgrade to netty-tcnative-1.1.33.Fork13 2016-02-17 08:17:13 -08:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport Enable shutdownOutput for EpollDomainSocketChannel 2016-02-18 18:09:48 -08:00
transport-native-epoll Enable shutdownOutput for EpollDomainSocketChannel 2016-02-18 18:09:48 -08:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +01:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-01-29 09:57:10 +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 Correctly set the alert type depending of the CertificateException 2016-02-19 08:28:55 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +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

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.