Norman Maurer
54b1a100f4
[maven-release-plugin] prepare for next development iteration
2016-08-26 10:06:32 +02:00
Norman Maurer
1208b90f57
[maven-release-plugin] prepare release netty-4.1.5.Final
2016-08-26 04:59:35 +02:00
Norman Maurer
cb7cf4491c
[maven-release-plugin] prepare for next development iteration
2016-07-27 13:29:56 +02:00
Norman Maurer
9466b32d05
[maven-release-plugin] prepare release netty-4.1.4.Final
2016-07-27 13:16:59 +02:00
Norman Maurer
047f6aed28
[maven-release-plugin] prepare for next development iteration
2016-07-15 09:09:13 +02:00
Norman Maurer
b2adea87a0
[maven-release-plugin] prepare release netty-4.1.3.Final
2016-07-15 09:08:53 +02:00
Norman Maurer
4676a2271c
[maven-release-plugin] prepare for next development iteration
2016-07-01 10:33:32 +02:00
Norman Maurer
ad270c02b9
[maven-release-plugin] prepare release netty-4.1.2.Final
2016-07-01 09:07:40 +02:00
Norman Maurer
4dec7f11b7
[maven-release-plugin] prepare for next development iteration
2016-06-07 18:52:34 +02:00
Norman Maurer
cf670fab75
[maven-release-plugin] prepare release netty-4.1.1.Final
2016-06-07 18:52:22 +02:00
Norman Maurer
6ca49d1336
[maven-release-plugin] prepare for next development iteration
2016-05-25 19:16:44 +02:00
Norman Maurer
446b38db52
[maven-release-plugin] prepare release netty-4.1.0.Final
2016-05-25 19:14:15 +02:00
Norman Maurer
572bdfb494
[maven-release-plugin] prepare for next development iteration
2016-04-10 08:37:18 +02:00
Norman Maurer
c6121a6f49
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-10 08:36:56 +02:00
Norman Maurer
6e919f70f8
[maven-release-plugin] rollback the release of netty-4.1.0.CR7
2016-04-09 22:13:44 +02:00
Norman Maurer
4cdd51509a
[maven-release-plugin] prepare release netty-4.1.0.CR7
2016-04-09 22:05:34 +02:00
Trustin Lee
3b941c2a7c
[maven-release-plugin] prepare for next development iteration
2016-04-02 01:25:05 -04:00
Trustin Lee
7368ccc539
[maven-release-plugin] prepare release netty-4.1.0.CR6
2016-04-02 01:24:55 -04:00
Norman Maurer
cee38ed2b6
[maven-release-plugin] prepare for next development iteration
2016-03-29 16:45:13 +02:00
Norman Maurer
9cd9e7daeb
[maven-release-plugin] prepare release netty-4.1.0.CR5
2016-03-29 16:44:33 +02:00
Norman Maurer
28d03adbfe
[maven-release-plugin] prepare for next development iteration
2016-03-21 11:51:50 +01:00
Norman Maurer
4653dc1d05
[maven-release-plugin] prepare release netty-4.1.0.CR4
2016-03-21 11:51:12 +01:00
Norman Maurer
ca443e42e0
[maven-release-plugin] prepare for next development iteration
2016-02-19 23:00:11 +01:00
Norman Maurer
f39eb9a6b2
[maven-release-plugin] prepare release netty-4.1.0.CR3
2016-02-19 22:59:52 +01:00
Norman Maurer
75a2ddd61c
[maven-release-plugin] prepare for next development iteration
2016-02-04 16:51:44 +01:00
Norman Maurer
7eb3a60dba
[maven-release-plugin] prepare release netty-4.1.0.CR2
2016-02-04 16:37:06 +01:00
Norman Maurer
1c417e5f82
[maven-release-plugin] prepare for next development iteration
2016-01-21 15:35:55 +01:00
Norman Maurer
c681a40a78
[maven-release-plugin] prepare release netty-4.1.0.CR1
2016-01-21 15:28:21 +01:00
Norman Maurer
2ecce8fa56
[maven-release-plugin] prepare for next development iteration
2015-11-10 22:59:33 +01:00
Norman Maurer
6a93f331d3
[maven-release-plugin] prepare release netty-4.1.0.Beta8
2015-11-10 22:50:57 +01:00
Norman Maurer
42e6b8fa86
[ #4289 ] Use a mock DNS Server for dns tests.
...
Motivation:
As relaying on external DNS Server can result to test-failures we should better use a mock DNS Server for the dns tests.
Modifications:
- Refactor the DnsNameResolverTest to use a mock DNS Server which is using apacheds.
- Allow to disable adding an opt resources as some servers not support it.
Result:
More stable testsuite.
2015-10-10 20:27:34 +02:00
Norman Maurer
2ff2806ada
[maven-release-plugin] prepare for next development iteration
2015-10-02 09:03:29 +02:00
Norman Maurer
5a43de10f7
[maven-release-plugin] prepare release netty-4.1.0.Beta7
2015-10-02 09:02:58 +02:00
Norman Maurer
34de2667c7
[maven-release-plugin] prepare for next development iteration
2015-09-02 11:45:20 +02:00
Norman Maurer
2eb444ec1d
[maven-release-plugin] prepare release netty-4.1.0.Beta6
2015-09-02 11:36:11 +02:00
Norman Maurer
f23b7b4efd
[maven-release-plugin] prepare for next development iteration
2015-05-07 14:21:08 -04:00
Norman Maurer
871ce43b1f
[maven-release-plugin] prepare release netty-4.1.0.Beta5
2015-05-07 14:20:38 -04:00
Norman Maurer
fce0989844
[maven-release-plugin] prepare for next development iteration
2015-03-03 02:06:47 -05:00
Norman Maurer
ca3b1bc4b7
[maven-release-plugin] prepare release netty-4.1.0.Beta4
2015-03-03 02:05:52 -05:00
Trustin Lee
e848066cab
Name resolver API and DNS-based name resolver
...
Motivation:
So far, we relied on the domain name resolution mechanism provided by
JDK. It served its purpose very well, but had the following
shortcomings:
- Domain name resolution is performed in a blocking manner.
This becomes a problem when a user has to connect to thousands of
different hosts. e.g. web crawlers
- It is impossible to employ an alternative cache/retry policy.
e.g. lower/upper bound in TTL, round-robin
- It is impossible to employ an alternative name resolution mechanism.
e.g. Zookeeper-based name resolver
Modification:
- Add the resolver API in the new module: netty-resolver
- Implement the DNS-based resolver: netty-resolver-dns
.. which uses netty-codec-dns
- Make ChannelFactory reusable because it's now used by
io.netty.bootstrap, io.netty.resolver.dns, and potentially by other
modules in the future
- Move ChannelFactory from io.netty.bootstrap to io.netty.channel
- Deprecate the old ChannelFactory
- Add ReflectiveChannelFactory
Result:
It is trivial to resolve a large number of domain names asynchronously.
2014-10-16 17:05:20 +09:00
