GitHub PushEvent at 2014-10-16 07:52:15
Repository: netty
Actor: trustin
Payload: {"shas":[["9d80f15ae9aabe5a77448f15b9e76bf22cb5c959","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Name resolver API and DNS-based name resolver\n\nMotivation:\n\nSo far, we relied on the domain name resolution mechanism provided by\nJDK.  It served its purpose very well, but had the following\nshortcomings:\n\n- Domain name resolution is performed in a blocking manner.\n  This becomes a problem when a user has to connect to thousands of\n  different hosts. e.g. web crawlers\n- It is impossible to employ an alternative cache/retry policy.\n  e.g. lower/upper bound in TTL, round-robin\n- It is impossible to employ an alternative name resolution mechanism.\n  e.g. Zookeeper-based name resolver\n\nModification:\n\n- Add the resolver API in the new module: netty-resolver\n- Implement the DNS-based resolver: netty-resolver-dns\n  .. which uses netty-codec-dns\n- Make ChannelFactory reusable because it's now used by\n  io.netty.bootstrap, io.netty.resolver.dns, and potentially by other\n  modules in the future\n  - Move ChannelFactory from io.netty.bootstrap to io.netty.channel\n  - Deprecate the old ChannelFactory\n  - Add ReflectiveChannelFactory\n\nResult:\n\nIt is trivial to resolve a large number of domain names asynchronously.","Trustin Lee",true],["1c7aa454ca4755370803d35b6bc70a48fb4e5461","8efd86fb78a56a5145ed7739dcb00c78581c5375@motd.kr","Fix test failures in ProxyHandlerTest\n\nMotivation:\n\nThe default name resolver attempts to resolve the bad host name (destination.com) and actually succeeds, making the ProxyHandlerTest fail.\n\nModification:\n\nUse NoopNameResolverGroup instead.\n\nResult:\n\nProxyHandlerTest passes again.","Trustin Lee",true]],"size":2,"ref":"refs/heads/name_resolver","head":"1c7aa454ca4755370803d35b6bc70a48fb4e5461"}