netty5/resolver/src/main/java/io/netty/resolver
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
..
AbstractAddressResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
AddressResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
AddressResolverGroup.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
DefaultAddressResolverGroup.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
DefaultNameResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
InetNameResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
InetSocketAddressResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
NameResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
NoopAddressResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
NoopAddressResolverGroup.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
package-info.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00
SimpleNameResolver.java Extract SocketAdress logic from NameResolver 2015-12-14 14:58:49 +01:00