2 ms·
Perhaps i misunderstand, but i feel like http2 push was trying to achieve something very different than websicket/ajax poling/long polling/sse. They dont seem c
by bawolff 2y ago
Perhaps i misunderstand, but i feel like http2 push was trying to achieve something very different than websicket/ajax poling/long polling/sse. They dont seem comparable to me at all.
- Lio 2y agoThat's an interesting point, would you mind elaborating on how you think the goals of HTTP2 Push differed? Even is if is a misunderstanding it would still be useful to consider.
- creesch 2y agoI don't know how to ask this without being quite direct. But why would you ask someone that when the differences are quite obvious? Certainly between web sockets (bidirectional, client initiated) and HTTP2 push (server initiated, one directional). Are you asking because you basically want to know more about the technologies? In that case why not frame it like that?
- deleted 2y ago[deleted]
- bawolff 2y agoHTTP2 is to hide connection latency by preloading. The other things are for bidirectional communication with a server. I would consider them very much apples and oranges. Its not just that they are designed for different purposes; i don't think it is possible to even use server push for the purpose websockets is used for in the browser.