Re:WebP: The WebPage Compression Format
by crote on Saturday September 07, 2024 @04:23PM
(#41476260)
In reality it's more like:
It's all about TCP congestion control here. There are dozens of algorithms used to handle it, but in pretty much all cases you want to have some kind of slow buildup in order to avoid completely swamping a slower connection and having all but the first few of your packets getting dropped.
[ Parent
| on HN ]
Re:WebP: The WebPage Compression Format
by notpushkin on Saturday September 07, 2024 @07:37PM
(#41477124)
> client acknowledges bytes 0-2k of X
Doesn’t client see reference to Y at this point? Modern browsers start parsing HTML even before they receive the whole document.
Not just modern. This was even more significant on slow connections, so they've kind of always done that. One could even argue that HTML, HTTP (specifically, chunked encoding) and gzip are all intentionally designed to enable this.
Re:WebP: The WebPage Compression Format
by account42 on Monday September 09, 2024 @05:34AM
(#41486810)
Chunked encoding is required for the server to start sending the document before it has been fully generated (or the size becomes known) but nothing stops the client from parsing not yet complete documents without it.