Go to file
Scott Mitchell 6d80c641e9 DNS Resolver should be more consistent with JDK resolution
Motivation:
If there are multiple DNS servers to query Java's DNS resolver will attempt to resolve A and AAAA records in sequential order and will terminate with a failure once all DNS servers have been exhausted. Netty's DNS server will share the same DnsServerAddressStream for the different record types which may send the A question to the first host and the AAAA question to the second host. Netty's DNS resolution also may not progress to the next DNS server in all situations and doesn't have a means to know when resolution has completed.

Modifications:
- DnsServerAddressStream should support new methods to allow the same stream to be used to issue multiple queries (e.g. A and AAAA) against the same host.
- DnsServerAddressStream should support a method to determine when the stream will start to repeat, and therefore a failure can be returned.
- Introduce SequentialDnsServerAddressStreamProvider for sequential use cases

Result:
Fixes https://github.com/netty/netty/issues/6926.
2017-07-05 09:10:59 -04:00
.github Use GitHub Issue/PR Template Feature 2016-12-07 11:40:26 -08:00
all [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
bom Add dependency management for missing entries 2017-06-14 20:26:33 +02:00
buffer Avoid a double check ByteBuf#ensureWritable in ByteBufUtil 2017-06-28 19:00:01 +02:00
codec Apply appropriate methods for writing CharSequence into ByteBuf 2017-06-27 07:58:39 +02:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-http Performance improvement for HttpRequestEncoder. Insert char into the string optimized. 2017-06-27 10:53:43 +02:00
codec-http2 Workaround IBM's J9 JVM getSupportedCipherSuites() returning SSL_ prefix cipher names 2017-07-05 09:05:42 -04:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-mqtt codec.mqtt: password and willMessage field types should be byte[] 2017-06-13 18:49:13 +02:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
codec-socks SocksCmdRequest and SocksCmdResponse are trying to convert host from IDN for the non-DOMAIN address types 2017-06-28 20:34:45 +02:00
codec-stomp Apply appropriate methods for writing CharSequence into ByteBuf 2017-06-27 07:58:39 +02:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
common Move methods for decode hex dump into StringUtil 2017-06-23 18:52:42 +02:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
example HTTP/2 HelloWorld clear text NPE 2017-06-21 06:55:28 +02:00
handler Workaround IBM's J9 JVM getSupportedCipherSuites() returning SSL_ prefix cipher names 2017-07-05 09:05:42 -04:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
license Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
microbench Performance improvement for HttpRequestEncoder. Insert char into the string optimized. 2017-06-27 10:53:43 +02:00
resolver [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
resolver-dns DNS Resolver should be more consistent with JDK resolution 2017-07-05 09:10:59 -04:00
tarball [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport Remove @deprecation keyword on AbstractUnsafe.ensureOpen(...) 2017-06-29 14:28:55 +02:00
transport-native-epoll Introduce EpollSocketChannelConfig.setTcpKeepCnt as replacement for setTcpKeepCntl. 2017-06-28 07:43:59 +02:00
transport-native-kqueue KQueue crash due to close/cleanup sequencing 2017-06-28 17:34:19 -04:00
transport-native-unix-common transport-native-kqueue libraries should not lazy link 2017-06-28 11:47:16 -04:00
transport-native-unix-common-tests fix UnixChannelUtil#isBufferCopyNeededForWrite 2017-06-24 21:27:54 -07:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-06-08 21:06:24 +02:00
transport-udt AbstractMethodError with barchart-udt 2017-07-05 07:35:32 +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: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
NOTICE.txt Remove reference to akka code and ArrayDeque which is not part of netty anymore 2017-03-07 21:30:51 +01:00
pom.xml Upgrade to netty-tcnative 2.0.5.Final 2017-06-25 19:03:33 +02:00
README.md Updating Branches to look section to match the current branching structure of the project 2016-03-10 22:08:01 +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.