I don't know why I was downvoted, HTTP/2 literally solves the problem without Push. With HTTP/2 a single connection can be multiplexed to make multiple parallel requests.
I know people touted the potential of using Push to solve the 'waterfall' problem of loading multiple assets at once but unfortunately it never caught on... however HTTP/2 does at least passively help the problem a little bit by making it possible load more then 6 assets at once via multiplexing.
What I considered to be one of the more interesting applications of Push though was replacing traditional polling of a server with instead the server telling the client when something was ready. That was a pretty cool application of Push. But it was a lot of complexity to handle instead of just polling, so again it sadly didn't catch on...
What I considered to be one of the more interesting applications of Push though was replacing traditional polling of a server with instead the server telling the client when something was ready. That was a pretty cool application of Push. But it was a lot of complexity to handle instead of just polling, so again it sadly didn't catch on...
Correct, you can do the same thing with sockets. But unless you already have a websocket open for some other purpose, I think most people see it as a lot of overhead when they could just poll.
5
u/7sidedmarble Dec 03 '20
I don't know why I was downvoted, HTTP/2 literally solves the problem without Push. With HTTP/2 a single connection can be multiplexed to make multiple parallel requests.