Hi,
we have stumbled upon the error below on Windows.
We suspect this is happening when closing sockets that have the linger
option set.
Since SocketDispatcher.close0() eventually calls the Windows API
closesocket(), this seems to be confirmed by this article:
https://msdn.microsoft.com/en-us/li
I have a very simple attempt to use the Java 10 / incubator httpclient api.
It works on "regular" resources, but fails horribly when attempting to get
things from localhost. It fails using 127.0.0.1, the actual non-loopback
IP, and the name localhost. The server is running, and presenting a very
si
Hi,
On Fri, Oct 16, 2015 at 12:35 PM, Pavel Rappo wrote:
> Hi,
>
> Here's a second update on the WebSocket API:
>
> webrev: http://cr.openjdk.java.net/~prappo/8087113/webrev.02/
> javadoc: http://cr.openjdk.java.net/~prappo/8087113/javadoc.02/
>
> Main differences from the previous version:
>
Hi,
On Fri, Sep 25, 2015 at 4:19 PM, Xuelei Fan wrote:
> Actually, it was a puzzle to me: whether a concrete server can support
> both HTTP/2 and HTTP/1.1, or not. If HTTP/2 mode of the server does not
> work, is it OK to fall-over to use HTTP/1.1 mode? I did not get the
> answer from the HTTP/2
