Stephane Landelle 6393506b97 Extract SocketAdress logic from NameResolver ... Motivation: As discussed in #4529, NameResolver design shouldn't be resolving SocketAddresses (or String name + port) and return InetSocketAddresses. It should resolve String names and return InetAddresses. This SocketAddress to InetSocketAddresses resolution is actually a different concern, used by Bootstrap. Modifications: Extract SocketAddress to InetSocketAddresses resolution concern to a new class hierarchy named AddressResolver. These AddressResolvers delegate to NameResolvers. Result: Better separation of concerns. Note that new AddressResolvers generate a bit more allocations because of the intermediate Promise and List<InetAddress>.		2015-12-14 14:03:50 +01:00
..
HttpProxyServer.java	Use Proxy-Authorization instead of Authorization for proxy authentication	2014-11-20 20:41:09 +09:00
ProxyHandlerTest.java	Extract SocketAdress logic from NameResolver	2015-12-14 14:03:50 +01:00
ProxyServer.java	Add proxy support for client socket connections	2014-10-14 12:29:08 +09:00
Socks4ProxyServer.java	Revamp io.netty.handler.codec.socksx	2015-02-10 09:14:13 +09:00
Socks5ProxyServer.java	Revamp io.netty.handler.codec.socksx	2015-02-10 09:14:13 +09:00
TestMode.java	Add proxy support for client socket connections	2014-10-14 12:29:08 +09:00
UnresponsiveHandler.java	Add proxy support for client socket connections	2014-10-14 12:29:08 +09:00