Go to file
pifuant ec91c40bf7 We should re-use the same handler instance as its sharable in the example
Motivation:

We should re-use the same handler instance as its sharable. 

Modification:

Re-use instance

Result:

More correct example
2018-05-30 09:09:18 +02:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
.mvn/wrapper Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
all [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
buffer Update the comment of io.netty.buffer.PoolChunk.java (#7934) 2018-05-14 15:44:32 +02:00
codec Correctly copy existing elements when CodecOutputList.add(index, element) is called. (#7939) 2018-05-15 19:41:45 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-http Run the WebSocketClientHandshaker08Test on the 08 implementation (#7974) 2018-05-27 10:02:49 +02:00
codec-http2 Correctly let Http2UnkownFrame extend HttpStreamFrame and so be usable with Http2MultiplexCodec. (#7976) 2018-05-29 07:27:40 +02:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
common Don't use VM.maxDirectMemory() on IBM J9 / Eclipse OpenJ9 to retrieve direct memory limit (#7966) 2018-05-25 14:35:32 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
docker Allow to test with boringssl-static and drop into shell (#7980) 2018-05-29 11:09:22 +02:00
example We should re-use the same handler instance as its sharable in the example 2018-05-30 09:09:18 +02:00
handler Use ByteBufAllocator used by the ReferenceCountedOpenSslEngine when build key-material. (#7952) 2018-05-18 19:36:57 +02:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
resolver [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite Ignore some test-flakiness when using Java11+ due outstanding Java11 bug. (#7984) 2018-05-29 19:48:40 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport AUTO_CLOSE should not be marked as deprecated. (#7967) 2018-05-24 21:25:30 +02:00
transport-native-epoll Read until all data is consumed when EOF is detected even if readPend… (#7961) 2018-05-24 20:29:29 +02:00
transport-native-kqueue Read until all data is consumed when EOF is detected even if readPend… (#7961) 2018-05-24 20:29:29 +02:00
transport-native-unix-common [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport-native-unix-common-tests Read until all data is consumed when EOF is detected even if readPend… (#7961) 2018-05-24 20:29:29 +02:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-05-14 11:11:45 +00:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitattributes Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
.gitignore Add docker-sync files to .gitignore 2018-05-15 10:39:14 +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
mvnw Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
mvnw.cmd Include mvn wrapper to make setup of development env easier 2018-01-26 08:13:17 +01:00
NOTICE.txt Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
pom.xml Don't trim stacktrace for exceptions when running mvn test (#7981) 2018-05-29 10:59:42 +02:00
README.md Provide an Automatic-Module-Name for the netty-all artifact fixes #7644 2018-01-27 20:31:16 +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.all
  • 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.