2021/9/17 3:03:25 -0700, aleksej.efi...@oracle.com:
> We had a discussion about the naming and decided to go with
> InetAddressResolverProvider and InetAddressResolver names.
> I will update the JEP text to reflect that.
That sounds fine.
- Mark
: Mark Reinhold
Cc: net-dev@openjdk.java.net ; Alan Bateman
Subject: Re: New candidate JEP: 418: Internet-Address Resolution SPI
Hi Mark,
Given Alan's input on "name service" term and providers naming convention, do
you still think that we should rename "java.net.spi.Ine
olver` - it might help to
highlight that it is used by `InetAddress` API.
Thanks,
Aleksei
From: Alan Bateman
Sent: Saturday, September 4, 2021 10:09 AM
To: Mark Reinhold ; Aleksej Efimov
Cc: net-dev@openjdk.java.net
Subject: Re: New candidate JEP: 418: Intern
On 03/09/2021 22:38, mark.reinh...@oracle.com wrote:
A suggestion, if I may ...
Consider using the term “resolver” instead of “name service,” especially
in the names of the SPI classes and interfaces.
That would avoid confusing the service of looking up names and addresses
with the service of p
A suggestion, if I may ...
Consider using the term “resolver” instead of “name service,” especially
in the names of the SPI classes and interfaces.
That would avoid confusing the service of looking up names and addresses
with the service of providing a service to look up names and addresses.
That
https://openjdk.java.net/jeps/418
Summary: Define a service-provider interface (SPI) for host name
and address resolution, so that java.net.InetAddress can make use of
resolvers other than the platform's built-in resolver.
- Mark
