On Wed, Dec 17, 2014 at 11:11 AM, Stuart Douglas <stuart.w.douglas_at_gmail.com
> wrote:
>
>
> I also think there's no such precedent. It must be hard decision for the
>> Java SE team to make such release.
>> My current thinking is that around the time of the release of Servlet
>> 4.0 and its implementations, there may be the official Java SE 9 release
>> with ALPN support.
>> So WAS vendors who don't have own JSSE provider or have difficulty to
>> make their own could resort to it.
>>
>
> So one thing I am not really clear on is what we are actually going to
> require in Servlet 4 / EE8, in particular:
>
> - Is HTTP2 a mandatory part of Servlet 4? i.e. you won't be certified
> compliant unless you support it
> - Is SE8 support required for compliance?
>
> If that is the case you basically have a situation where you can't
> actually be compliant unless you modify the JVM's boot class path (I guess
> you could support HTTP2 over upgrade, but afaik most browsers are not
> planning to implement this).
>
> Stuart
>
>
I've been thinking about real-life usages, but I've missed the point that
you addressed.
In this circumstance, making TCK test cases for 'h2' (HTTP/2 over TLS) on
Java SE 8 could be also a problem.
Eugene