Go to file
Trustin Lee b62c5290ed Let SniHandler accept Mapping as well as DominaNameMapping
Related: #4470 #4473

Motivation:

A user might want to:

- implement dynamic mapping from hostname to SslContext
- server large number of domain names whose SslContext can be
  initialized lazily and destroyed when unused

Modifications:

- Let SniHandler accept Mapping<String, SslContext> as well as
  DomainNameMapping
- Make the default constructor of SslContext so that a user can create
  his or her own SslContext wrapper

Result:

Flexibility
2015-12-18 12:36:26 +09:00
all [maven-release-plugin] prepare for next development iteration 2015-11-10 22:59:33 +01:00
buffer Throw ReadOnlyBufferException if unsafe buffer is used and dst is direct 2015-12-17 13:25:21 +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 HTTP/2 Weighted Fair Queue Byte Distributor 2015-12-17 11:17:02 -08: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 HTTP/2 Weighted Fair Queue Byte Distributor 2015-12-17 11:17:02 -08:00
example Revamp the Http2ConnectionHandler builder API 2015-12-17 14:08:13 +09:00
handler Let SniHandler accept Mapping as well as DominaNameMapping 2015-12-18 12:36:26 +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 HTTP/2 Weighted Fair Queue Byte Distributor 2015-12-17 11:17:02 -08:00
resolver Have hosts file support for DnsNameResolver, close #4074 2015-12-17 15:15:42 +01:00
resolver-dns Have hosts file support for DnsNameResolver, close #4074 2015-12-17 15:15:42 +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 HTTP/2 Weighted Fair Queue Byte Distributor 2015-12-17 11:17:02 -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.