Stephane Landelle 541fe86fe0 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:58:49 +01:00
..
src/main/java/io/netty/resolver	Extract SocketAdress logic from NameResolver	2015-12-14 14:58:49 +01:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2015-03-03 08:30:59 -05:00