Conversation

http long polling is still one of the most funniest hackiest invention ever

Sep 6, 2021

this is up there with, live stream over gif

Sep 6, 2021

ter explaination http long polling works by sending a request, and the server only responding once it got a notification, so you would have a http request open for like ages live stream over gif is just,, keep responding with new gif frames to a gif http request

Replying to

these both seem like 100% legit things to do via http

Replying to

It was 100% legitimate before WebSockets. HTTP/2 obsoletes WebSockets outside the browser since you can multiplex bidirectional streams over the same persistent connection. WebSockets are now essentially just a workaround for not having access to that from JS in a browser.

eater "cum carbonation"

Replying to

and

saying http/2 obsoletes websockets sounds like a bit of a stretch, but look at what people actually used it and pushed others to use it for I can see why that can be a conclusion

Replying to

and

It has bidirectional binary streams. It essentially has a more flexible equivalent to WebSockets at the protocol level instead of built on top of it. It's a separate thing from the push feature. They essentially built the WebSocket functionality into it.

web.dev

Introduction to HTTP/2

HTTP/2 (or h2) is a binary protocol that brings push, multiplexing streams and frame control to the web.

Replying to

Bidirectional binary streams... Like a socket has?

Daniel Micay

@DanielMicay

Replying to

@EndlessMason

SCTP sockets, sure, since it's a message-based protocol. HTTP/2 isn't actually a good implementation of this for real-time use due to being implemented on top of TCP. It's awkward. HTTP/3 fixes it by moving to a more modern take on SCTP with baseline authenticated encryption.

12:09 AM · Sep 7, 2021Twitter Web App

eater "cum carbonation"

Replying to

and

http/3 being QUIC here?

Replying to

and

Yes, HTTP/3 is basically HTTP/2 via QUIC with messages/streams in higher level protocol mapping to the lower-level ones. WebRTC was built on top of SCTP over DTLS over UDP and QUIC is basically a more modern replacement for that with improved congestion control, encryption, etc.

Show replies

Replying to

and

HTTP/2 has all the issues tied to TCP along with messages and streams blocking each other since TCP has no clue that isn't a bunch of separate streams. Still way friendlier to servers, routers, etc. than opening a dozen TCP connections to server as was done for HTTP/1.1 though.

Replying to

and

Normally, an HTTP/2 connection gives you ~128 concurrent streams and each of those is message-based. The problem is that it's all being done through a TCP connection oblivious to messages and streams. It might have made more sense to just skip right to the HTTP/3 approach.