net-dev  

Messages by Thread

• • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException Jaikiran Pai
  • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException Aleksei Efimov
  • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException Daniel Fuchs
  • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException [v2] Aleksei Efimov
  • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException [v2] Daniel Fuchs
  • Re: RFR: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException [v2] Jaikiran Pai
  • Integrated: 8332686: InetAddress.ofLiteral can throw StringIndexOutOfBoundsException Aleksei Efimov
• RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Jaikiran Pai
  • Re: RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Christian Stein
  • Re: RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Daniel Fuchs
  • Re: RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Jaikiran Pai
  • Re: RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Daniel Fuchs
  • Re: RFR: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Jaikiran Pai
  • Integrated: 8345375: Improve debuggability of test/jdk/java/net/Socket/CloseAvailable.java Jaikiran Pai
• RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration Volkan Yazıcı
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v3] Volkan Yazıcı
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v3] Volkan Yazıcı
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration [v3] duke
  • Integrated: 8344229: Revisit SecurityManager usage in jdk.httpserver after JEP 486 integration Volkan Yazıcı
• Integrated: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs Volkan Yazıcı
• HTTP/2 Support in jdk.httpserver? Josiah Noel
  • Re: HTTP/2 Support in jdk.httpserver? robert engels
  • Re: HTTP/2 Support in jdk.httpserver? Josiah Noel
  • Re: HTTP/2 Support in jdk.httpserver? Robert Engels
  • Re: HTTP/2 Support in jdk.httpserver? Josiah Noel
  • Re: HTTP/2 Support in jdk.httpserver? Jaikiran Pai
  • Re: HTTP/2 Support in jdk.httpserver? Josiah Noel
• RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error Jaikiran Pai
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error [v2] Jaikiran Pai
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error [v2] Daniel Jeliński
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error Daniel Fuchs
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error Daniel Fuchs
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error [v2] Jaikiran Pai
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error [v2] Daniel Fuchs
  • Re: RFR: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error [v2] Daniel Jeliński
  • Withdrawn: 8227493: Return a more useful error message from lookupAllHostAddr if getaddrinfo results in EAI_SYSTEM error duke
• RFR: 8345286: Remove use of SecurityManager API from misc areas Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas Alan Bateman
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Severin Gehwolf
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6] Alan Bateman
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v7] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6] Alan Bateman
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v6] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v4] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Severin Gehwolf
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v3] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Severin Gehwolf
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v2] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v5] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v5] Severin Gehwolf
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v5] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v3] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v7] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Sean Mullan
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Alan Bateman
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Severin Gehwolf
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Daniel Fuchs
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v8] Daniel Fuchs
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Alan Bateman
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Jaikiran Pai
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Kevin Walls
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Kevin Walls
  • Re: RFR: 8345286: Remove use of SecurityManager API from misc areas [v9] Jaikiran Pai
  • Integrated: 8345286: Remove use of SecurityManager API from misc areas Jaikiran Pai
• Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Jaikiran Pai
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] David Holmes
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Jaikiran Pai
  • Re: RFR: 8342868: Errors related to unused code on Windows after 8339120 in core libs [v2] Julian Waters
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] duke
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v27] Jaikiran Pai
• RFR: 8345074: java.net.InterfaceAddress constructor could be made private Eirik Bjørsnøs
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private Eirik Bjørsnøs
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private Chen Liang
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private [v2] Eirik Bjørsnøs
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private [v2] Eirik Bjørsnøs
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private [v2] Jaikiran Pai
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private [v2] Jaikiran Pai
  • Re: RFR: 8345074: java.net.InterfaceAddress constructor could be made private [v2] Eirik Bjørsnøs
  • Integrated: 8345074: java.net.InterfaceAddress constructor could be made private Eirik Bjørsnøs
• RFR: 8345249: Apply some conservative cleanups in FileURLConnection Eirik Bjørsnøs
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection Eirik Bjørsnøs
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection Chen Liang
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection Eirik Bjørsnøs
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection [v2] Eirik Bjørsnøs
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection [v2] Jaikiran Pai
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection [v2] Daniel Jeliński
  • Re: RFR: 8345249: Apply some conservative cleanups in FileURLConnection [v2] Eirik Bjørsnøs
  • Integrated: 8345249: Apply some conservative cleanups in FileURLConnection Eirik Bjørsnøs
• RFR: 7038838: Unspecified NPE in java.net.IDN methods Jaikiran Pai
  • Re: RFR: 7038838: Unspecified NPE in java.net.IDN methods Chen Liang
  • Re: RFR: 7038838: Unspecified NPE in java.net.IDN methods Daniel Fuchs
  • Re: RFR: 7038838: Unspecified NPE in java.net.IDN methods Jaikiran Pai
  • Integrated: 7038838: Unspecified NPE in java.net.IDN methods Jaikiran Pai
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v26] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v25] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v24] Volkan Yazıcı
• RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear Jaikiran Pai
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear Daniel Fuchs
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear Jaikiran Pai
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear Michael McMahon
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v3] Jaikiran Pai
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v2] Jaikiran Pai
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v2] Daniel Fuchs
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v3] Jaikiran Pai
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v3] Daniel Fuchs
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v3] Michael McMahon
  • Re: RFR: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear [v3] Jaikiran Pai
  • Integrated: 8235786: Javadoc for com/sun/net/httpserver/HttpExchange.java#setAttribute is unclear Jaikiran Pai
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v23] Volkan Yazıcı
• RFR: 8345223: Remove doPrivileged in java.base/unix/classes/sun/net and java.base/macosx/classes/java/net classes after JEP 486 integration Daniel Fuchs
  • Re: RFR: 8345223: Remove doPrivileged in java.base/unix/classes/sun/net and java.base/macosx/classes/java/net classes after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8345223: Remove doPrivileged in java.base/unix/classes/sun/net and java.base/macosx/classes/java/net classes after JEP 486 integration [v2] Alan Bateman
  • Re: RFR: 8345223: Remove doPrivileged in java.base/unix/classes/sun/net and java.base/macosx/classes/java/net classes after JEP 486 integration [v2] Aleksei Efimov
  • Re: RFR: 8345223: Remove doPrivileged in java.base/unix/classes/sun/net and java.base/macosx/classes/java/net classes after JEP 486 integration [v2] Volkan Yazıcı
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v2] Michael McMahon
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v2] Daniel Fuchs
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v2] Michael McMahon
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v3] Daniel Fuchs
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v4] Daniel Fuchs
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v4] Daniel Fuchs
  • Re: RFR: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration [v4] Alan Bateman
  • Integrated: 8345223: Remove stray doPrivileged in java.base java.net and sun.net classes after JEP 486 integration Daniel Fuchs
• RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure Daniel Fuchs
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v2] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v2] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v2] Daniel Fuchs
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v2] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v3] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v3] Daniel Fuchs
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v3] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v4] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v4] Daniel Fuchs
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v4] Volkan Yazıcı
  • Re: RFR: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure [v4] duke
  • Integrated: 8345176: Add tests to verify java.net.Socket constructors close the socket on failure Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Alan Bateman
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v22] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v21] Volkan Yazıcı
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v20] Volkan Yazıcı
• Re: RFR: 8337143: (fc, fs) Move filesystem-related native objects from libnio to libjava [v10] Brian Burkhalter
• Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Volkan Yazıcı
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Daniel Fuchs
  • Re: RFR: 8343791: Socket.connect API should document whether the socket will be closed when hostname resolution fails or another error occurs [v19] Volkan Yazıcı

• Earlier messages
• Later messages