Go to file
Norman Maurer 5b239150f1 HeadContext is inbound and outbound (#8592)
Motivation:

Our HeadContext in DefaultChannelPipeline does handle inbound and outbound but we only marked it as outbound. While this does not have any effect in the current code-base it can lead to problems when we change our internals (this is also how I found the bug).

Modifications:

Construct HeadContext so it is also marked as handling inbound.

Result:

More correct code.
2018-11-24 10:48:13 +01: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 Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01:00
bom Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01:00
buffer Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-dns Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-haproxy Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-http Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-http2 Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-memcache Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-mqtt Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-redis Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-smtp Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-socks Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-stomp Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
codec-xml Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
common Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
dev-tools Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
docker Update to openjdk 12ea19 (#8487) 2018-11-09 16:50:58 +01:00
example Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01:00
handler Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
handler-proxy Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
resolver Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
resolver-dns Combine flushes in DnsNameResolver to allow usage of sendmmsg to reduce syscall costs (#8470) 2018-11-21 06:42:50 +01:00
tarball Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
testsuite Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01:00
testsuite-autobahn Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
testsuite-http2 Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
testsuite-osgi Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01:00
testsuite-shading Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
transport HeadContext is inbound and outbound (#8592) 2018-11-24 10:48:13 +01:00
transport-native-epoll Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
transport-native-kqueue Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
transport-native-unix-common Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
transport-native-unix-common-tests Update version number to start working on Netty 5 2018-11-20 15:49:57 +01:00
transport-sctp Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01: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 Exclude mainframer related files from git 2018-10-14 13:20:18 +02: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 Remove OIO transport (and transports that depend on it). (#8580) 2018-11-21 15:23:18 +01: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.