http2

This may just highlight some misconception of mine, but I was curious: If you had an HTTP/2 server running and wanted to make XHR requests in the browser to the server, would XHR automatically take advantage of the performance optimisations in headers and such that it provides? Or would it ignore that functionality and operate as an HTTP request? If so, are there any things we can do to use the new optimisations in our requests? You don't need to do anything. If the server supports HTTP/2, XHR will use it. Header compression and such will kick in automatically. Test it: Open an HTTP/2 website

I went thru this page: https://www.eclipse.org/jetty/documentation/9.3.x/alpn-chapter.html to have an ALPN boot jar in my classpath and still I can't get it working. I am confused as to know if I need an Open SDK Java 8 than Oracle Java 8. My Java version is: java -version java version "1.8.0_11" Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode) And I'm using the following versions of Jetty and ALPN boot: <jetty-version>9.4.0.M1</jetty-version> <alpn-version>8.1.9.v20160720</alpn-version> <dependency> <groupId>org.mortbay.jetty

http/2 is much better than http for websites. It's very helpful if you have to make multiple http calls. But is there any significant benefit for a single call? There are general considerations and specific considerations. The general considerations is that HTTP/2, being a binary protocol, is much easier to implement and has many less corner cases than HTTP/1.1. For example, the fact that HTTP/1.1 headers needs to parsed without knowing in advance header name length and header value length. Another example is whether the HTTP/1.1 parser needs to support obsolete line folding in headers. There

Unlike stateless HTTP/1.0, HTTP/2 has stateful components. These parts appear stateful: opportunistic encryption framing layer header blocks This part appears to be stateless: application layer Are there any other parts of HTTP/2 are stateful? 来源： https://stackoverflow.com/questions/33682693/which-parts-of-http-2-are-stateful

I'm starting a new project and I'm trying to be forward thinking about it. I've used Browserify in the past. For my new project I would like to use either Webpack, Rollup, or SystemJS. Webpack looks by far to be the most mature with tons of awesome features. I'm concerned, though, that Webpack is going to be irrelevant in a year or two with the adoption of HTTP/2. So I'm wondering, what value does Webpack offer for a site being served over HTTP/2? I'm not looking for an opinion, but a factual explanation of the benefits of using Webpack with HTTP/2. If there are no benefits, or very little

How does HTTP2 solve Head of Line blocking (HOL) issue? This problem is very frequent in http1.1, but I heard HTTP2 has fixed this problem. Could someone explain how exactly HTTP2 fixed the problem? HTTP Head of line blocking Head of Line blocking in HTTP terms is often referring to the fact that each browser/client has a limited number of connections to a server and doing a new request over one of those connections has to wait for the ones before to complete before it can fire it off. The head of line requests block the subsequent ones. HTTP/2 solves this by introducing multiplexing so that