r.java, which essentially boils down to
using
the URI/URL constructor that constructs a hierarchical URI from the given
components
Regardless of whether the fixes are back-ported to jdk11u, is there a shared
view in
this mailing list that we pick one pattern on tip for consistency, I'm happy to
Nikola has opened an issue to cover the loopback address range and we're
preparing a patch:
https://bugs.openjdk.java.net/browse/JDK-8255264
We've identified some unit tests to include in the patch, does
gtest/runtime/test_os_windows.cpp seem the appropriate location for them?
Patch (preview):
Modified Windows specific loopback macros to support full range of loopback
addresses, commit message includes unit test data as there's no gtest's for
java libraries (only hotspot compiler)
This is an expansion on the original fix for 8250521: Configure initial RTO to
use minimal retry for loo
Have an RFR needing a sponsor and review - this is related to Nikola's prior
work on JDK-8250521: Configure initial RTO to use minimal retry for loopback
connections on Windows
Thanks in advance
Mat Carter
Sent from Outlook
From: net-dev on behalf of Mat Carter
Sent: Tuesday, Decem
On Wed, 23 Dec 2020 16:10:27 GMT, Alan Bateman wrote:
>> Modified Windows specific loopback macros to support full range of loopback
>> addresses, commit message includes unit test data as there's no gtest's for
>> java libraries (only hotspot compiler)
>>
>> This is an expansion on the origin
On Mon, 30 Nov 2020 18:09:57 GMT, Mat Carter
wrote:
> Modified Windows specific loopback macros to support full range of loopback
> addresses, commit message includes unit test data as there's no gtest's for
> java libraries (only hotspot compiler)
>
> This is an
