2015-05-13 22:57 GMT+02:00 Mark Thomas <ma...@apache.org>: > Just a quick overview to save folks digging through the commit messages. > > If you want to play with this you'll need: > - APR + tc-native build from *trunk* (to get ALPN support). > - an EC based cert or set the FireFox option > network.http.spdy.enforce-tls-profile to false > > I've been testing with FireFox 38.0 and the examples application. > > To see what is going on, enable debug logging for the > org.apache.coyote.http2 package. > > With the current code: > - the connection prefaces are sent / received and processed > - additional settings frames are processed > - priority frames are processed > - header frames are partially processed (the decoded headers and values > are logged) > > In terms of what this means for a basic working HTTP/2 implementation > (i.e. one that works with simple requests but breaks for anything > remotely close to an edge case) > - You can see the initial connection set-up > - You can see the initial streams set up (to create a dependency > hierarchy with priorities to manage relative priorities of subsequent > requests) > - You can see the initial request > - And then the connection fails. > > The HPACK decoder is working (thanks to Stuart Douglas and remm - that > made today a lot more productive). >
Very good overall progress. From my testing the decoder/encoder appeared to be working very well, and uses the Tomcat structures so it is supposed to be usable as is. Obviously if there's anything to fix there, I'll have to contribute it back. > > The next steps are to get a basic implementation working which means: > - figure out how to feed requests into Tomcat's processing chain > - figure out how to extract the response back into the HTTP/2 > implementation. > > Is it really a good idea to use the same API for HTTP/2 servlets ? I haven't seen anything going on in the expert group. Rémy
