Go to file
Scott Mitchell 08cb650b64 Consistent use of SSLHandshakeException for ALPN
Motiviation:
The OpenSSL engine uses SSLHandshakeException in the event of failures that occur during the handshake process. The alpn-boot project's getSSLException will also map the no_application_protocol to a SSLHandshakeException exception. We should be consistent and use SSLHandshakeException for handshake failure events.

Modifications:
-Update JdkAlpnSslEngine to propagate an SSLHandshakeException in the event of a failure.

Result:
Consistent usage of SSLHandshakeException during a handshake failure event.
2015-05-26 16:10:43 -07:00
all [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
buffer Expose metrics for PooledByteBufAllocator 2015-05-20 21:01:37 +02:00
codec [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
codec-http Support empty http responses when using compression 2015-05-26 10:06:25 +02:00
codec-socks [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
common [#3805] Fix incorrect javadoc in PlatformDependent 2015-05-25 21:42:21 +02:00
example SCTP echo client/server multi-homing examples 2015-05-22 22:24:18 +02:00
handler Consistent use of SSLHandshakeException for ALPN 2015-05-26 16:10:43 -07: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-05-07 11:33:47 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
testsuite [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:01:51 +02:00
transport-native-epoll Not try to write more then Integer.MAX_VALUE / SSIZE_MAX via writev 2015-05-21 12:01:51 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04:00
transport-udt [maven-release-plugin] prepare for next development iteration 2015-05-07 11:33:47 -04: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 Upgrading Jetty alpn-api version 2015-05-22 13:15:21 -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.