Go to file
Jon Chambers e6842b4561 Expose channel pool configuration to subclasses.
Motivation:

`SimpleChannelPool` subclasses are likely to override the `connectChannel` method, and are likely to clobber the cloned `Bootstrap` handler in the process. To allow subclasses to properly notify the pool listener of new connections, we should expose (at least) the `handler` property of the pool to subclasses.

Modifications:

Expose `SimpleChannelPool` properties to subclasses via `protected` getters.

Result:

Subclasses can now use the bootstrap, handler, health checker, and health-check-on-release preoperties from their superclass.
2016-12-21 20:51:56 +01:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:46 -08:00
all Support compiling netty with Java9 2016-12-03 20:41:19 +01:00
buffer Remove usage of own Atomic*FieldUpdater in favor of JDKs 2016-12-15 08:21:52 +00:00
codec Eliminate usage of releaseLater(...) to reduce memory usage during tests 2016-11-18 11:21:23 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
codec-http Add unit test for HttpObjectDecoder with message split on buffer boundaries 2016-12-20 13:07:21 -08:00
codec-socks Support compiling netty with Java9 2016-12-03 20:41:19 +01:00
common Revert "Disallow setting logger factory twice" 2016-12-21 15:16:10 +01:00
example [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
handler Explicit disable support of SSL / TLS Compression 2016-12-16 08:26:06 +00: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-10-14 14:32:28 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
testsuite Eliminate usage of releaseLater(...) to reduce memory usage during tests 2016-11-18 11:21:23 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
transport Expose channel pool configuration to subclasses. 2016-12-21 20:51:56 +01:00
transport-native-epoll Remove usage of own Atomic*FieldUpdater in favor of JDKs 2016-12-15 08:21:52 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2016-10-14 14:32:28 +02: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:53:28 +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: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 Allow to run tests with extra commandline arguments 2016-12-08 10:49:20 +01:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:09:30 +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

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.