On 03/11/2014 22:08, Mark Thomas wrote: <snip/>
> I've been spending the last hour or so looking at our current SPDY > implementation. We are going to have issues there as well. It targets > SPDY/2 which most browsers no longer support. Servlet 4.0 is targeting > HTTP/2 which is going to be roughly SPDY/4+ > > I don't know how much of the existing SPDY code is going to make sense > with HTTP/2 but I do know what we currently have is broken with most > browsers. I'm currently leaning towards excluding the current SDPY code > from the build until the connector refactoring is complete and then look > at it more closely to figure out what we can keep, what needs > refactoring and what needs to go. I found an alternative solution. I've performed an untested migration of the SPDY/2 proxy (the bit that depended on BIO) to NIO so we can leave the SPDY code alone for the initial connector refactoring and come back to it when work starts on HTTP/2. <snip/> Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
