non-blocking SocketChannel connect broken on Windows 8 (original) (raw)
Alan Bateman Alan.Bateman at oracle.com
Thu Sep 29 08:35:26 PDT 2011
- Previous message: non-blocking SocketChannel connect broken on Windows 8
- Next message: Code Review Request: 6953455 CookieStore.add() cannot handle null URI parameter, contrary to the API specification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeroen Frijters wrote:
: It's definitely a behavior change in Windows 8 and I agree that it probably has some compatibility impact, but fundamentally I think that the OpenJDK code is wrong, unless there is documentation somewhere that claims that the socket will be bound when the async connect is initiated. We're assuming connect/getsockname work like they do on Unix/Linux so this isn't the first time we've been caught out by Windows differences.
I'll create a bug for this as this will clearly break existing code.
-Alan.
- Previous message: non-blocking SocketChannel connect broken on Windows 8
- Next message: Code Review Request: 6953455 CookieStore.add() cannot handle null URI parameter, contrary to the API specification
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]