2015-04-02 22:33 GMT+02:00 Mark Thomas <ma...@apache.org>: > I've been spending some time thinking about how to plumb in HTTP/2 > support into the Tomcat 9 code base. After a couple of failed starts I > think I have a good starting point that will be able to support NPN, > ALPN and HTTP upgrade without making too much mess of the existing code. > > Before I commit it, I'd like to test it and that brings me to a small > problem. The methods to set/get NPN protocols for OpenSSL are only > available in tc-native trunk. > > OpenSSL has support for NPN in 1.0.1 and ALPN in 1.0.2. NPN is > essentially deprecated in favour of ALPN but it looks like NPN will be > around for a while. > > Given that OpenSSL support for 0.9.8 and 1.0.0 will cease at the end of > this year, I'd like to propose the following: > > 1. Switch the focus of tc-native development to trunk. > > 2a. tc-native trunk will require OpenSSL 1.0.1. > or > 2b. tc-native trunk will require OpenSSL 1.0.2. > > 3. tc-native 1.1.x will move to a bug-fix only mode. > > 4. Tomcat 9.0.x will require a minimum of at least 1.2.0. > > Discussion of possible variations: > 2a/b. Requiring a minimum of 1.0.2 would enable us to use ALPN rather > than the deprecated NPN. I'm +0.5 for this. > > Thoughts? Assuming folks are broadly in favour, I'd like to get a build > of tc-native 1.2.0-dev for Windows up at > http://people.apache.org/~markt/dev/ for folks to play with next week. > > Ok for this plan :) And for the non native, I would vote to require Java 9.
Also, I will add the new IO I talked about earlier. Rémy
