4 ms·

I guess you should outline the cases you care the most about, for anyone to be able to answer if there is any material performance improvements.

• hansvm 2y ago
  The only requirements are serving a lot of the same "kind" of content, enough such (or for some other business reason) that it doesn't make sense to send it all at once, and somebody willing to spend a bit of time to implement it. Map and local geocoding information comes to mind as a decent application, and if the proposed implementation weren't so hyper-focused on common compression standards you could probably do something fancy for, e.g., meme sites (with a finite number of common or similar background images). Assuming (perhaps pessimistically) it won't work well for most sites serving images, other possibilities include: - Real-estate searches (where people commonly tweak tons of parameters and geographies, returning frequently duplicated information like "This historical unit has an amazing view in each of its 2 bedrooms"). - Expanding that a bit, any product search where you expect a person to, over time, frequently query for the same sorts of stuff. - Local business information (how common is it to open at 10am and close at 6pm every weekday in some specific locale for example). ... If the JS, image, and structural HTML payloads dwarf everything else then maybe it won't matter in practice. I bet somebody could make good use of it though.