2 ms·
HTTP/2 multiplexes requests over one socket connection, so it should solve most of problems you state.
HTTP/2 multiplexes requests over one socket connection, so it should solve most of problems you state.
Except browsers do not allow Push on http/2 so far
clients don't have any api to get at data pushed by http/2 - it is not a websocket replacement and can't be used for the same things. http/2 will be used to multiplex static resources to clients - not application data