Go to file
Norman Maurer c1b1d6268a Allow to detect failed query caused by an Timeout / IO error and also not cache these.
Motivation:

At the moment there is not way for the user to know if resolving a domain was failed because the domain was unkown or because of an IO error / timeout. If it was caused by an timeout / IO error the user may want to retry the query. Also if the query was failed because of an IO error / timeout we should not cache it.

Modifications:

- Add DnsNameResolverTimeoutException and include it in the UnkownHostException if the domain could not be resolved because of an timeout. This will allow the user to retry the query when inspecting the cause.
- Do not cache IO errors / timeouts
- Add unit test

Result:

Easier for users to implement retries for DNS querys and not cache IO errors / timeouts.
2017-11-23 10:56:41 +01: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-11-08 22:36:53 +00:00
bom [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
buffer AbstractByteBuf readSlice bound check bug 2017-11-18 09:03:42 +01:00
codec DefaultHttpHeader.names().toArray(...) may throw ArrayStoreException 2017-11-22 19:04:55 +01:00
codec-dns [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-haproxy [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-http DefaultHttpHeader.names().toArray(...) may throw ArrayStoreException 2017-11-22 19:04:55 +01:00
codec-http2 HttpConversionUtil TE filtering robustness 2017-11-22 08:45:11 +01:00
codec-memcache [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-mqtt [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-redis [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-smtp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-socks [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-stomp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
codec-xml [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
common HttpHeaders valuesIterator and contains improvements 2017-11-20 08:34:06 -08:00
dev-tools [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
example [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
handler Dont fire an SslHandshakeEvent if the handshake was not started at all. 2017-11-16 19:57:04 +01:00
handler-proxy [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00: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 HttpMethod#valueOf improvement 2017-11-20 11:07:50 -08:00
resolver [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
resolver-dns Allow to detect failed query caused by an Timeout / IO error and also not cache these. 2017-11-23 10:56:41 +01:00
tarball [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-autobahn [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
testsuite-osgi [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport Improved error message in FixedChannelPool 2017-11-13 20:29:07 +01:00
transport-native-epoll Not directly call getsockopt but use exported helper function 2017-11-22 08:40:44 +01:00
transport-native-kqueue [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-native-unix-common Not directly call getsockopt but use exported helper function 2017-11-22 08:40:44 +01:00
transport-native-unix-common-tests [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00:00
transport-udt [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00: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 [maven-release-plugin] prepare for next development iteration 2017-11-08 22:36:53 +00: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.