@jaffathecake @slightlylate if disk cache matching worked "offline" for assets would this solve/replace a big use case for service workers?
-
-
Replying to @samccone @jaffathecake
Not if I understand the question correctly.
1 reply 0 retweets 1 like -
There are 2 major problems to solve re: offline. 1: getting code running to mediate subsequent requests 2: handling app deps gracefully
3 replies 0 retweets 2 likes -
Replying to @slightlylate @jaffathecake
yeah, my thought was .. if you have a cache time of 1 week on all your assets, and are offline, why can't the browser use the cached files?
1 reply 0 retweets 2 likes -
The browser can do that right now for subresources with current HTTP caching semantics. Pattern 1 at https://jakearchibald.com/2016/caching-best-practices/ …
1 reply 0 retweets 1 like -
Replying to @jeffposnick @samccone and
But for navigation targets or any other URLs that can't include versioning, it's not "safe".https://developers.google.com/web/fundamentals/primers/service-workers/high-performance-loading …
1 reply 0 retweets 1 like -
Right; the question isn't "can the browser use it?" it's "can I have confidence that the browser *will* use it?"
1 reply 0 retweets 0 likes
Until/unless you're managing the resources yourself and can introspect what's available via script, answer is "no, not really".
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.