Re: HTTP/2 progress report

2015-05-29 11:13 GMT+02:00 Mark Thomas : > On 15/05/2015 19:46, Rémy Maucherat wrote: > > 2015-05-13 22:57 GMT+02:00 Mark Thomas : > > > > >> The next steps are to get a basic implementation working which means: > >> - figure out how to feed requests into Tomcat's processing chain > >> - figure o

Re: HTTP/2 progress report

On 29/05/2015 10:20, Rainer Jung wrote: > Am 29.05.2015 um 11:13 schrieb Mark Thomas: >> On 15/05/2015 19:46, Rémy Maucherat wrote: >>> 2015-05-13 22:57 GMT+02:00 Mark Thomas : >> >> >> The next steps are to get a basic implementation working which means: - figure out how to feed request

Re: HTTP/2 progress report

Am 29.05.2015 um 11:13 schrieb Mark Thomas: On 15/05/2015 19:46, Rémy Maucherat wrote: 2015-05-13 22:57 GMT+02:00 Mark Thomas : 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

Re: HTTP/2 progress report

On 15/05/2015 19:46, Rémy Maucherat wrote: > 2015-05-13 22:57 GMT+02:00 Mark Thomas : >> 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 >> i

Re: HTTP/2 progress report

2015-05-13 22:57 GMT+02:00 Mark Thomas : > 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.enforc

HTTP/2 progress report

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 FireFo

Re: HTTP/2 progress report

2015-04-08 23:56 GMT+02:00 Mark Thomas : > As of r1672190 we now have the following: > > - ALPN support in tc-native trunk > - The ability to register upgrade protocol implementations that will: > - be included in the ALPN negotiation > - cause processing to be passed to a protocol dedicated p

HTTP/2 progress report

As of r1672190 we now have the following: - ALPN support in tc-native trunk - The ability to register upgrade protocol implementations that will: - be included in the ALPN negotiation - cause processing to be passed to a protocol dedicated processor implementation once ALPN negotiation com