JEP 321: HTTP Client (Standard)

[Chris Hegarty]

> On 4 Dec 2017, at 21:56, David Lloyd <david.lloyd at redhat.com> wrote:
> ...
>> You mention general-purpose concepts such as ByteBufferReference and
>> ByteBufferPool. Note that these are tiny implementation classes (150 lines
>> in total) and not exposed in the API.
> 
> Yes they are, currently - at least ByteBufferReference is at the heart of it:
> 
> http://hg.openjdk.java.net/jdk/jdk/file/6dcbdc9f99fc/src/jdk.incubator.httpclient/share/classes/jdk/incubator/http/AsyncConnection.java#l61 <http://hg.openjdk.java.net/jdk/jdk/file/6dcbdc9f99fc/src/jdk.incubator.httpclient/share/classes/jdk/incubator/http/AsyncConnection.java#l61>
> 
> And that class relies directly on ByteBufferPool in its own API.
> 
> Unless the jdk/jdk branch does not reflect the latest incarnation of
> this JEP, in which case I definitely haven't have been up to date with
> it, despite following this list.


Sorry, before replying further, there is clearly some confusion here. As Alan already said, the above types are NOT part of the API, they are non-public implementation.

The ‘http-client-branch’ of the JDK sandbox [1] contains the very latest code.

-Chris.

[1] http://hg.openjdk.java.net/jdk/sandbox/branches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/net-dev/attachments/20171204/f6628d2f/attachment.html>