Here are refreshed links to the latest code in the sandbox:



a) Changes to address the two issues raised by Simone during
   the JEP Propose To Target [1] [2].

b) Changes to address review comments from dfuchs, prappo,
   michaelm, and chegar [3].

c) Several bug fixes, additional test coverage, and stability


[1] https://bugs.openjdk.java.net/browse/JDK-8201325
[2] https://bugs.openjdk.java.net/browse/JDK-8201361
[3] http://hg.openjdk.java.net/jdk/sandbox/log?revcount=80&rev=desc%28%22review+comment%22%29+and+branch%28%22http-client-branch%22%29+and+date%28%22%3E2018-02-01%22%29

On 21/03/18 20:33, Chris Hegarty wrote:

This is a request for review for the HTTP Client implementation - JEP 321.

The javadoc link has been refreshed, based on feedback received from
the CSR [1] ( and a follow on supplementary CSR [2] ):

The webrev link has been refreshed to include implementation changes
to support the latest API, additional test code coverage and scenarios:

On 9 Feb 2018, at 14:33, Chris Hegarty <chris.hega...@oracle.com> wrote:
Development of the JDK HTTP Client, incubated in JDK 9 and re-incubated
in JDK 10, has continued. It will soon be in a position to be proposed
for inclusion in Java 11, through JEP 321. This will proceed, as usual,
through the JEP 2.0 process.

JEP 321 has recently been updated with the proposed package and module
name, `java.net.http`. The code in the sandbox has been updated to
reflect this.

Javadoc based on the latest code in the sandbox:

Webrev based on the latest code in the sandbox:

( much of the changes in the webrev are mechanical due to renaming, but
  there are stability fixes and the API documentation has been
  reorganized to improve readability )

More information about the JDK HTTP Client can be found on the
networking groups page.


[1] https://bugs.openjdk.java.net/browse/JDK-8197565
[2] https://bugs.openjdk.java.net/browse/JDK-8199938

Reply via email to