From sritter at azul.com  Thu Feb 16 15:49:09 2017
From: sritter at azul.com (Simon Ritter)
Date: Thu, 16 Feb 2017 15:49:09 +0000
Subject: HTTP/2 Client
Message-ID: <69a5e005-ff8e-1716-f9c3-aaec45a59479@azul.com>

Can someone confirm whether the HTTP/2 client work is being included in 
JDK 9?  According to the list of JEPs on the OpenJDK project page [1], 
JEP 110 is a feature.  However, in the EDR this is not referenced.  The 
JEP [2] itself shows the relase target as 9, but only talks in terms of 
a prototype.  Given that we are now feature complete this is a little 
confusing.

Thanks,

Simon.

[1] http://openjdk.java.net/projects/jdk9/
[2] http://openjdk.java.net/jeps/110

From mark.reinhold at oracle.com  Thu Feb 16 15:55:20 2017
From: mark.reinhold at oracle.com (mark.reinhold at oracle.com)
Date: Thu, 16 Feb 2017 07:55:20 -0800
Subject: HTTP/2 Client
In-Reply-To: <69a5e005-ff8e-1716-f9c3-aaec45a59479@azul.com>
References: <69a5e005-ff8e-1716-f9c3-aaec45a59479@azul.com>
Message-ID: <20170216075520.139711231@eggemoggin.niobe.net>

2017/2/16 7:49:09 -0800, Simon Ritter <sritter at azul.com>:
> Can someone confirm whether the HTTP/2 client work is being included in 
> JDK 9?  According to the list of JEPs on the OpenJDK project page [1], 
> JEP 110 is a feature.  However, in the EDR this is not referenced.  The 
> JEP [2] itself shows the relase target as 9, but only talks in terms of 
> a prototype.  Given that we are now feature complete this is a little 
> confusing.

JEP 110 identifies itself as a JDK incubator module in its title, and
includes this text in its summary:

  The API will be delivered as an incubator module with JDK 9 as defined
  in the incubator JEP 11.  This implies:

    - The API and implementation will not be part of Java SE.

    - The API will live under the jdk.incubator namespace.

    - The module will not resolve by default at compile or run time.

This is why it is not mentioned in the EDR.

- Mark

From sritter at azul.com  Thu Feb 16 16:05:53 2017
From: sritter at azul.com (Simon Ritter)
Date: Thu, 16 Feb 2017 16:05:53 +0000
Subject: HTTP/2 Client
In-Reply-To: <20170216075520.139711231@eggemoggin.niobe.net>
References: <69a5e005-ff8e-1716-f9c3-aaec45a59479@azul.com>
 <20170216075520.139711231@eggemoggin.niobe.net>
Message-ID: <f3ddae74-5cf8-feda-02a1-63af2e7de0af@azul.com>

Mark,
thanks for the clarification.

Regards,

Simon.

On 16/02/2017 15:55, mark.reinhold at oracle.com wrote:
> 2017/2/16 7:49:09 -0800, Simon Ritter <sritter at azul.com>:
>> Can someone confirm whether the HTTP/2 client work is being included in
>> JDK 9?  According to the list of JEPs on the OpenJDK project page [1],
>> JEP 110 is a feature.  However, in the EDR this is not referenced.  The
>> JEP [2] itself shows the relase target as 9, but only talks in terms of
>> a prototype.  Given that we are now feature complete this is a little
>> confusing.
> JEP 110 identifies itself as a JDK incubator module in its title, and
> includes this text in its summary:
>
>    The API will be delivered as an incubator module with JDK 9 as defined
>    in the incubator JEP 11.  This implies:
>
>      - The API and implementation will not be part of Java SE.
>
>      - The API will live under the jdk.incubator namespace.
>
>      - The module will not resolve by default at compile or run time.
>
> This is why it is not mentioned in the EDR.
>
> - Mark