Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770)

fergald left a comment (w3c/ServiceWorker#1770)

I don't think allowing large files will have much impact on total temporary space used. People are already caching them, just in a non-ergonomic way, e.g. using blobs in IndexedDB or breaking them into chunks. See e.g. https://developer.chrome.com/docs/ai/cache-models .

Given that it's a legit and increasingly common thing to do, we should make it ergonomic. I am slightly concerned that it becomes easy to *accidentally* use a huge amount of space but it's not like there are lots of URLs out there that will unexpectedly yield a 10G response.

The rise of these huge files means that browsers should have better UIs for managing and tidying disk space. Ensuring that these files are in `CacheStorage`, associated with their original URL allows for better UX. They are much more deleteable (or preserverable) than  if they were stored as a blob in IndexedDB or broken into chunks in OPFS.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1770#issuecomment-2914635927
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1770/2914635927@github.com>