> On 27 Sep 2018, at 11:51, Norman Maurer wrote:
>
> Forgot to ask… is it somehow possible to “subscribe” to an issue and get
> notified once there are some updates ?
Yes, you can “watch” an issue, component, or subcomponent, BUT
you need to be, at least, an OpenJDK author.
Unfortunately, I
Forgot to ask… is it somehow possible to “subscribe” to an issue and get
notified once there are some updates ?
Bye
Norman
> On 27. Sep 2018, at 12:18, Norman Maurer wrote:
>
> Thanks a lot.
>
> That would provide exactly what we need in netty.
>
> Bye
> Norman
>
>
>> On 27. Sep 2018, at
Thanks a lot.
That would provide exactly what we need in netty.
Bye
Norman
> On 27. Sep 2018, at 12:09, Chris Hegarty wrote:
>
> Norman,
>
>> On 26 Sep 2018, at 12:45, Norman Maurer wrote:
>>
>> BTW I am happy to open an enhancement request for this with more details .
>> Just wanted to c
Norman,
> On 26 Sep 2018, at 12:45, Norman Maurer wrote:
>
> BTW I am happy to open an enhancement request for this with more details .
> Just wanted to check in first here :)
I searched the bug database to ensure that this request had
not come up before, and found nothing. I took the liberty
BTW I am happy to open an enhancement request for this with more details . Just
wanted to check in first here :)
Just let me know if I should do or not.
Bye
Norman
> On 26. Sep 2018, at 13:15, Norman Maurer wrote:
>
> Yeah preferable a method for both but JNDI works for the nameservers for n
Yeah preferable a method for both but JNDI works for the nameservers for now.
> Am 26.09.2018 um 13:06 schrieb Chris Hegarty :
>
> Hi Norman,
>
> A non-blocking DNS resolver, good use-case.
>
> Clearly the system configured name servers are of interest too ( I bring
> it up since your specific
Hi Norman,
A non-blocking DNS resolver, good use-case.
Clearly the system configured name servers are of interest too ( I bring
it up since your specific request is about search domains )? Search
domains are only part of the problem.
I assume you can retrieve the name servers through the JDNI A
Yeah… In netty we an DNS resolver implementation that is completely
non-blocking and for this we need it to correctly resolve in some cases.
Blocking DNS resolution just doesn’t “cut it” when you use non-blocking IO and
also need to resolve a lot of stuff during connect etc.
Bye
Norman
> On
Hi Norman,
As you correctly found, there is a private implementation that is used
by JNDI. As far as I am aware, there are no plans to provide a Java SE
API for retrieving the default search domain list. Is there a particular
use-case that you have in mind that requires this?
-Chris.
On 26/09/1
