>>>>> On Tue, 09 Dec 2014 12:42:17 +0000, Mark Thomas <markt_at_apache.org> said:
MT> On 08/12/2014 20:44, Edward Burns wrote:
>>>>>>> On Thu, 27 Nov 2014 13:49:03 +0900, Eugene Chung() <euigeun_chung_at_tmax.co.kr> said:
EC> HTTP/2 requires ALPN extension(rfc7301) for HTTP/2 over TLS.
EC> But Servlet 4.0(Java EE 8) will be based on Java SE 8, which is already
EC> released.
EC> Java SE 8, exactly JSSE in it, doesn't support ALPN extension.
EC> I have been investigating but I couldn't find the way to use ALPN in a
EC> standard fashion for container developers.
EC> Is there any plan for this? (endorsed JSSE for Java SE 8?)
EC> Or any other standard mechanism that I don't know?
EB> My plan of record is to leave this as an implementation detail. Yes, I
EB> know there is an ALPN client coming in Java SE 9, but we will be
EB> sticking with Java SE 8 as our base.
MT> That is a pretty large implementation detail. Is there nothing we can do
MT> here in terms of requesting a back-port of the ALPN client to Java
MT> 8?
I am willing to try. I must set one precondition before I can credibly
make such a request: establish a precedent. Is there any precedent for
such a large new feature, with significant public API, to be introduced
in a "dot release" of Java SE? I know of none off the top of my head,
but I know I have many gaps up there, particularly the older I get.
MT> It seems like a missed opportunity to require each container to figure
MT> out a way to make this work for them on Java 8.
Such missed opportunities are the breeding ground for useful FOSS, such
as the work on ALPN in Jetty. I know that's cold comfort for the Tomcat
community, but perhaps Apache HTTPClient cold add support for ALPN?
Ed
--
| edward.burns_at_oracle.com | office: +1 407 458 0017
| 50 days til DevNexus 2015
| 60 days til JavaLand 2015
| 70 days til CONFESS 2015