After just getting finished reading RFC 7540, HTTP/2 does obsolete websockets for all use cases except for pushing binary data from the server to a JS webclient. HTTP/2 fully supports binary bidi streaming (read on), but browser JS doesn’t have an API for consuming binary data frames and AFAIK such an API is not planned. … Read more
In my case it was – no disk space left on the web server.
In general, the biggest immediate benefit of HTTP/2 is the speed increase offered by multiplexing for the browser connections which are often hampered by high latency (i.e. slow round trip speed). These also reduce the need (and expense) of multiple connections which is a work around to try to achieve similar performance benefits in HTTP/1.1. … Read more
Put simply, multiplexing allows your Browser to fire off multiple requests at once on the same connection and receive the requests back in any order. And now for the much more complicated answer… When you load a web page, it downloads the HTML page, it sees it needs some CSS, some JavaScript, a load of … Read more