3 ms·
Fun fact: similar things, but much more general, were in the HTTP/1.1 standard from 1997. However, HTTP frames relied on HTTP chunks, which were fundamentally b
by masswerk 5y ago
Fun fact: similar things, but much more general, were in the HTTP/1.1 standard from 1997. However, HTTP frames relied on HTTP chunks, which were fundamentally broken in the Win-HTTP-stack implementation. (Third party browsers like Netscape Navigator or Opera implemented a HTTP-stack of their own, but IE relied on the built-in implementation.)
(Because of this flaw, keep-alive was broken, as well, and requests stalled until they timed out. Which is, why everyone set the request timeout to just a short period and you couldn't type a HTTP request manually in a terminal anymore.)
- bawolff 5y agoIf you mean multipart/x-mixed-replace, that's still a part of the html5 spec.
- ComputerGuru 5y agoBarely. Google nerfed it and now it is only supported for images. You could do full-on chat without JS by using it for the html itself previously.
- masswerk 5y agoI wouldn't know a browser that would still support it. Because of said issues, it didn't see any significant use (apart from a few enthusiastic experiments early on.)
- statico 5y agoAn example of that is the clock on this page: https://www.plover.com/~mjd/swatch.html https://www.plover.com/~mjd/swatch.html