- From: Sam Richard <notifications@github.com>
- Date: Thu, 25 Jul 2019 14:54:49 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 25 July 2019 21:55:12 UTC
@b1tr0t I was having a bit of a discussion around this, and I think either of the following scenarios for updating would be good: * Serve stale, but otherwise obey HTTP caching rules (as you mentioned) (Stale-While-Revalidate in Workbox parlance) * Always serve from cache, only refresh on Service Worker install event (Cache First in Workbox parlance) I think the "Stale-While-Revalidate" method is likely least surprising for developers, even though it may lead to additional downloads if HTTP cache headers aren't set well, whereas the "Cache First" method wold ensure no additional downloads but may not feel intuitive for developers if they push updates to just that file. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/774#issuecomment-515229383
Received on Thursday, 25 July 2019 21:55:12 UTC