net-dev  

Messages by Thread

• • Re: RFR: 8357406: Remove usages of jdk.tracePinnedThreads system property from httpclient tests SendaoYan
  • Integrated: 8357406: Remove usages of jdk.tracePinnedThreads system property from httpclient tests Jaikiran Pai
  • Re: RFR: 8357406: Remove usages of jdk.tracePinnedThreads system property from httpclient tests Jaikiran Pai
• RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v2] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v3] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v4] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Shaojin Wen
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Shaojin Wen
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v5] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v6] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Valerie Peng
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v7] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v8] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v9] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Alan Bateman
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v10] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v11] Per Minborg
  • Re: RFR: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() [v11] Alan Bateman
  • Integrated: 8357268: Use JavaNioAccess.getBufferAddress rather than DirectBuffer.address() Per Minborg
• RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Chen Liang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Joe Darcy
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base ExE Boss
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Alan Bateman
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Alan Bateman
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Daniel Fuchs
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Chen Liang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v2] Weijun Wang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Nizar Benalla
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Weijun Wang
  • Re: RFR: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base [v3] Nizar Benalla
  • Integrated: 8356632: Fix remaining {@link/@linkplain} tags with refer to private/protected types in java.base Nizar Benalla
• RFR: 8357013: Optimize response code parsing in HttpURLConnection Patrick Strawderman
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Patrick Strawderman
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: Optimize response code parsing in HttpURLConnection Daniel Fuchs
  • Re: RFR: 8357013: HttpURLConnection#getResponseCode can avoid substring call when parsing to int duke
  • Integrated: 8357013: HttpURLConnection#getResponseCode can avoid substring call when parsing to int Patrick Strawderman
• The default HttpServer Executor Josiah Noel
  • Re: The default HttpServer Executor Daniel Fuchs
  • Re: The default HttpServer Executor Josiah Noel
  • Re: The default HttpServer Executor Ethan McCue
  • Re: [External] : Re: The default HttpServer Executor Daniel Fuchs
  • Re: [External] : Re: The default HttpServer Executor Josiah Noel
• RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v2] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Daniel Fuchs
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Michael McMahon
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] duke
  • Re: RFR: 8351347: HttpClient Improve logging of response headers [v3] Volkan Yazici
  • Integrated: 8351347: HttpClient Improve logging of response headers Volkan Yazici
• RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v2] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Hai-May Chao
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v3] Hai-May Chao
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v3] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Sean Mullan
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v4] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v5] Artur Barashev
  • Re: RFR: 8353113: Peer supported certificate signature algorithms are not being checked with default SunX509 key manager [v6] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v7] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v8] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v9] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v10] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v11] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v12] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Sean Mullan
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v13] Artur Barashev
  • Re: RFR: 8359956: Support algorithm constraints and certificate checks in SunX509 key manager [v14] Artur Barashev
• RFR: 8356644: Update encoding declaration to UTF-8 Magnus Ihse Bursie
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Daniel Fuchs
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Phil Race
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Naoto Sato
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Sergey Bylokhov
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Magnus Ihse Bursie
  • Re: RFR: 8356644: Update encoding declaration to UTF-8 Sergey Bylokhov
  • Integrated: 8356644: Update encoding declaration to UTF-8 Magnus Ihse Bursie
• RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Stefan Karlsson
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leonid Mesnik
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Daniel Fuchs
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leonid Mesnik
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Alan Bateman
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Daniel Fuchs
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Daniel Fuchs
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Stefan Karlsson
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Stefan Karlsson
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Daniel Fuchs
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Phil Race
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Christian Stein
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Phil Race
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor David Holmes
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Christian Stein
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor David Holmes
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Re: RFR: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
  • Withdrawn: 8356171: Increase timeout for testcases as preparation for change of default timeout factor Leo Korinth
• RFR: 8355360: -d option of jwebserver command should accept relative paths Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths Alan Bateman
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v2] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v2] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v3] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v3] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v4] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v4] Daniel Fuchs
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v4] Volkan Yazici
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v4] duke
  • Re: RFR: 8355360: -d option of jwebserver command should accept relative paths [v4] Michael McMahon
  • Integrated: 8355360: -d option of jwebserver command should accept relative paths Volkan Yazici
• RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified kieran-farrell
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] kieran-farrell
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Chen Liang
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] kieran-farrell
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Chen Liang
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] kieran-farrell
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Jaikiran Pai
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Michael McMahon
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Michael McMahon
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] duke
  • Re: RFR: 7046003: Default value of Authenticator.getRequestingURL() is not specified [v2] Jaikiran Pai
  • Integrated: 7046003: Default value of Authenticator.getRequestingURL() is not specified kieran-farrell
• RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method kieran-farrell
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method Daniel Fuchs
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v2] kieran-farrell
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v2] Michael McMahon
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v2] Daniel Fuchs
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v3] kieran-farrell
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v2] kieran-farrell
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v3] kieran-farrell
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress.getBroadcast() method [v3] Daniel Fuchs
  • Re: RFR: 8356395: Spec needs to be clarified for InterfaceAddress class level API documentation and getBroadcast() method [v3] duke
  • Integrated: 8356395: Spec needs to be clarified for InterfaceAddress class level API documentation and getBroadcast() method kieran-farrell
• Re: RFR: 8337143: (fc, fs) Move filesystem-related native objects from libnio to libjava [v13] Brian Burkhalter
• RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Per Minborg
  • Re: RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Per Minborg
  • Re: RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Shaojin Wen
  • Re: RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Chen Liang
  • Re: RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Per Minborg
  • Re: RFR: 8356255: Add Stable Field Updaters to allow efficient lazy field evaluations Chen Liang

• Earlier messages
• Later messages