Go to file
Norman Maurer 8189399e9d Ignore EINTR on close(...) as there is nothing sane we can do.
Motivation:

If close(...) reports EINTR there is nothing sane we can do so it makes no sense to even report it. See also:

https://github.com/apple/swift-nio/pull/217

Modifications:

Just ignore EINTR when calling close(...)

Result:

Less noise in the logs.
2018-03-23 07:39:17 +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 [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
bom [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
buffer FixedCompositeByteBuf should allow to access memoryAddress / array when wrap a single buffer. 2018-03-13 08:50:42 +01:00
codec Add tests for EmptyHeaders 2018-03-20 15:59:08 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-http When the response exceeds the threshold, it will be compressed 2018-02-25 16:43:45 +01:00
codec-http2 Correctly include the stream id when convert from Http2HeadersFrame to HttpMessage 2018-03-17 09:46:01 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
common Correctly record creation stacktrace in ResourceLeakDetector. 2018-03-16 08:24:18 +01:00
dev-tools [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
docker Provide a Docker image for reproducible builds 2018-01-22 20:02:17 +01:00
example [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
handler Skip NPN tests when libressl 2.6.1+ is used. 2018-03-22 08:30:49 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
license Add the NOTICE of the forked portion of Apache Harmony 2018-01-30 11:22:51 +01:00
microbench Copies from read-only heap ByteBuffer to direct ByteBuf can avoid stealth ByteBuf allocation and additional copies 2018-02-27 09:54:21 +09:00
resolver [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
resolver-dns [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
tarball [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
testsuite Call correct super methods in test. 2018-02-27 09:52:32 +09:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
testsuite-http2 [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
transport Simplify DefaultChannelGroup.contains(...) and so remove one instanceof check. 2018-03-17 09:45:24 +01:00
transport-native-epoll Flush task should not flush messages that were written since last flush attempt. 2018-03-02 10:09:40 +09:00
transport-native-kqueue Flush task should not flush messages that were written since last flush attempt. 2018-03-02 10:09:40 +09:00
transport-native-unix-common Ignore EINTR on close(...) as there is nothing sane we can do. 2018-03-23 07:39:17 +01:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +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 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
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 [maven-release-plugin] prepare for next development iteration 2018-02-21 12:52:33 +00: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.