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
..
main/java/io/netty/handler/proxy	ByteString introduced as AsciiString super class	2015-04-14 16:35:17 -07:00
test/java/io/netty/handler/proxy	Extract SocketAdress logic from NameResolver	2015-12-14 14:03:50 +01:00