3 ms·
Yes, websockets follow an HTTP upgrade path and can't leverage datagrams. An breaking update in the HTTP spec would be quite painful, especially for backend li
by jeroenhd 4y ago
Yes, websockets follow an HTTP upgrade path and can't leverage datagrams.
An breaking update in the HTTP spec would be quite painful, especially for backend libraries that are often updated only when absolutely necessary.
The fact the API isn't even finished yet, let alone standardised, also makes it a good idea to add it as a new feature. I don't think browsers should mess with standardised protocols to implement some draft that's still in progress because they're very likely to break something, especially since this particular type of socket is only available to a small number of websites and use cases (those on servers supporting transferring raw HTTP/3 to the application server, so probably not most CDN/DDoS protection services).