Go to file
Norman Maurer aabb73a9d2 Add SniCompletionEvent which allows to easily retrieve the hostname that was used to select the SslContext.
Motivation:

At the moment its a bit "hacky" to retrieve the hostname that was used during SNI as you need to hold a reference to SniHandler and then call hostname() once the selection is done. It would be better to fire an event to let the user know we did the selection.

Modifications:

Add a SniCompletionEvent that can be used to get the hostname that was used to do the selection and was included in the SNI extension.

Result:

Easier usage of SNI.
2017-12-06 14:09:11 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
buffer Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-dns EDNS Client Subnet is not encoded correctly when source prefix length is not a multiple of 8. 2017-12-01 08:14:13 +01:00
codec-haproxy Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-http Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-http2 Http2ConnectionHandler Http2ConnectionPrefaceAndSettingsFrameWrittenEvent propagation 2017-12-02 08:23:28 +01:00
codec-memcache Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-mqtt Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-redis Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-smtp Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-socks Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-stomp Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
codec-xml Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
common Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
handler Add SniCompletionEvent which allows to easily retrieve the hostname that was used to select the SslContext. 2017-12-06 14:09:11 +01:00
handler-proxy Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench HttpMethod#valueOf improvement 2017-11-20 11:07:50 -08:00
resolver Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
resolver-dns Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-osgi Provide a test for #6548 using the OSGi test suite 2017-11-27 19:49:15 +01:00
transport DefaultMaxMessagesRecvByteBufAllocator support an option to ignore maybeMoreData 2017-12-04 11:03:58 -08:00
transport-native-epoll Not use safeRelease(...) but release(...) to release non-readable holders to ensure we not mask errors. 2017-12-04 20:38:35 +01:00
transport-native-kqueue Not use safeRelease(...) but release(...) to release non-readable holders to ensure we not mask errors. 2017-12-04 20:38:35 +01:00
transport-native-unix-common Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-rxtx Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
transport-sctp Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
transport-udt Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Use shaded dependency on JCTools instead of copy and paste 2016-06-10 13:19:45 +02: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 Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Update to conscrypt 1.0.0.CR13 2017-12-04 21:25:59 +01:00
README.md Adding stable JDK9 module names that follow reverse-DNS style 2017-11-29 11:50:24 +01:00
run-example.sh Add UptimeServer and adjust UptimeClient's code style. 2017-04-28 07:41:07 +02: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

Development of all 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.

Usage with JDK 9

Netty can be used in modular JDK9 applications as a collection of automatic modules. The module names follow the reverse-DNS style, and are derived from subproject names rather than root packages due to historical reasons. They are listed below:

  • io.netty.buffer
  • io.netty.codec
  • io.netty.codec.dns
  • io.netty.codec.haproxy
  • io.netty.codec.http
  • io.netty.codec.http2
  • io.netty.codec.memcache
  • io.netty.codec.mqtt
  • io.netty.codec.redis
  • io.netty.codec.smtp
  • io.netty.codec.socks
  • io.netty.codec.stomp
  • io.netty.codec.xml
  • io.netty.common
  • io.netty.handler
  • io.netty.handler.proxy
  • io.netty.resolver
  • io.netty.resolver.dns
  • io.netty.transport
  • io.netty.transport.epoll (native omitted - reserved keyword in Java)
  • io.netty.transport.kqueue (native omitted - reserved keyword in Java)
  • io.netty.transport.unix.common (native omitted - reserved keyword in Java)
  • io.netty.transport.rxtx
  • io.netty.transport.sctp
  • io.netty.transport.udt

Automatic modules do not provide any means to declare dependencies, so you need to list each used module separately in your module-info file.