@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 -
The shared http cache doesn't give you anything re: #1. AppCache shows how tortured that can get when you don't let script handle things.
1 reply 0 retweets 1 like -
All sane solutions to #2 build on whatever you decide re problem 1.
1 reply 0 retweets 1 like -
AppCache, e.g., forced most app-level data & dynamic resource dependencies away from HTTP & REST because no cache assurances
1 reply 0 retweets 1 like -
Super hard to build things sanely when cache might *partially* evict your app. So it's not about introspection (although that matters).
1 reply 0 retweets 1 like
Big-ticket item is atomic eviction. Apps need to be able to charge dynamic resources to quota (ala IDB), else system is unusable
-
-
There are also major privacy issues w/ shared cache introspection, but you don't have to consider them to understand why CacheStorage exists
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.