On Sun, 17 Oct 2021 21:03:56 GMT, Mark Sheppard wrote:
> getByName requires a hostname lookup and getByAdress requires (eventually - I
> know the docs says there’s no reverse lookup) an address reverse lookup.
> Thus, a logical mapping is getByName —> lookupHostname, and getByAddr —>
>
On Sun, 17 Oct 2021 21:39:06 GMT, Mark Sheppard wrote:
> I think that a hostname is constant while a host is up, but it can be
> changed, and when changed a host restart is required. I don't think it is
> quite as dynamic as has been suggested, but I open to correction.
It is possible to
On Fri, 15 Oct 2021 17:19:26 GMT, Daniel Fuchs wrote:
>> Aleksei Efimov has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - Add @since tags to new API classes
>> - Add checks and test for empty stream resolver results
>
>
On Fri, 15 Oct 2021 17:09:46 GMT, Daniel Fuchs wrote:
>> Aleksei Efimov has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - Add @since tags to new API classes
>> - Add checks and test for empty stream resolver results
>
>
On Fri, 15 Oct 2021 14:25:02 GMT, Daniel Fuchs wrote:
>> Aleksei Efimov has updated the pull request incrementally with two
>> additional commits since the last revision:
>>
>> - Add @since tags to new API classes
>> - Add checks and test for empty stream resolver results
>
>
On Sun, 17 Oct 2021 15:55:59 GMT, Aleksei Efimov wrote:
> > So Suggestion is refector remove Configuration to simplify the interface
> > and provide the BULITIN_RESOLVER and hostname as parameters to the
> > InetAddressResolverProvider::get method
>
> During work on this JEP we've examined
On Sun, 17 Oct 2021 16:33:57 GMT, Aleksei Efimov wrote:
> > What’s in a name? I find the method names of the InetAddressResolver
> > interface a bit ambiguous. Typically in this DNS problem space one speaks
> > of lookup to resolve a hostname to its associated addresses and reverse
> > lookup
On Sun, 17 Oct 2021 15:55:59 GMT, Aleksei Efimov wrote:
> * `InetAddressResolverProvider.Configuration` interface API might evolve,
> e.g. there might be a need to pass additional configuration items.
> * local hostname is a dynamic information, therefore it cannot be passed as
> string
On Sat, 16 Oct 2021 10:48:32 GMT, Mark Sheppard wrote:
> What’s in a name? I find the method names of the InetAddressResolver
> interface a bit ambiguous. Typically in this DNS problem space one speaks of
> lookup to resolve a hostname to its associated addresses and reverse lookup
> to
On Sat, 16 Oct 2021 12:30:44 GMT, Mark Sheppard wrote:
> So Suggestion is refector remove Configuration to simplify the interface and
> provide the BULITIN_RESOLVER and hostname as parameters to the
> InetAddressResolverProvider::get method
During work on this JEP we've examined the approach
On Tue, 12 Oct 2021 15:43:24 GMT, Aleksei Efimov wrote:
>> This change implements a new service provider interface for host name and
>> address resolution, so that java.net.InetAddress API can make use of
>> resolvers other than the platform's built-in resolver.
>>
>> The following API
On Tue, 12 Oct 2021 15:43:24 GMT, Aleksei Efimov wrote:
>> This change implements a new service provider interface for host name and
>> address resolution, so that java.net.InetAddress API can make use of
>> resolvers other than the platform's built-in resolver.
>>
>> The following API
On Tue, 12 Oct 2021 15:43:24 GMT, Aleksei Efimov wrote:
>> This change implements a new service provider interface for host name and
>> address resolution, so that java.net.InetAddress API can make use of
>> resolvers other than the platform's built-in resolver.
>>
>> The following API
On Tue, 12 Oct 2021 15:43:24 GMT, Aleksei Efimov wrote:
>> This change implements a new service provider interface for host name and
>> address resolution, so that java.net.InetAddress API can make use of
>> resolvers other than the platform's built-in resolver.
>>
>> The following API
> This change implements a new service provider interface for host name and
> address resolution, so that java.net.InetAddress API can make use of
> resolvers other than the platform's built-in resolver.
>
> The following API classes are added to `java.net.spi` package to facilitate
> this:
>
15 matches
Mail list logo
