- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Feb 2025 17:38:24 +0000
- To: public-css-archive@w3.org
> maybe you want to do less fine-grained incremental downloads? Ah. With the old `patch-subset` approach, the client provided a list of - what it could render - what it wanted to render and the server computed a patch for _exactly that._ But this was a cache-buster, required a special server, and was a potential privacy leak. With the current approach, the initial font contains tables of (urls to) patches, along with what is in each one. The client doesn't communicate with a server except to request some patch files. Of course the client can request patches for more than it currently needs; and as the patches are pre-computed (and thus, the same for everyone, and cacheable) they tend to not be very fine grained. But still, it could be a useful hint for the client. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6485#issuecomment-2691206654 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 February 2025 17:38:25 UTC