@jaffathecake @marcosc : and if you want HTTP eviction behaviour, just don't use the SW Cache API; SWs sit "in front" of netstack
-
-
Replying to @slightlylate
@jaffathecake@marcosc : that means anything fetch()'d from a SW will hit HTTP cache on the way out. SW cache solves a different problem.1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@jaffathecake the assets are synthetically generated by the page tho. Not on network.1 reply 0 retweets 2 likes -
Replying to @marcosc
@slightlylate@jaffathecake don't know if it helps, but concrete example (search for saveBinaryToCache) https://github.com/mozilla/remote-newtab/pull/66/files …1 reply 0 retweets 0 likes -
Replying to @marcosc
@marcosc: this is a case where you want your own TTL logic (and I'd assume a separate cache for these assets). /cc@jaffathecake1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@jaffathecake yep, already got multiple caches. Will add logic, but maybe something for v2 spec?1 reply 0 retweets 1 like -
Replying to @marcosc
@marcosc: it comes up more than I anticipated, but what most folks seem to want is "auto discard", not HTTP semantics /cc@jaffathecake2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@marcosc although you want "auto discard" to discard least-frequently used assets, but the definition of "used" is tricky3 replies 0 retweets 0 likes -
Replying to @jaffathecake
@jaffathecake Well, you have the classic eviction policies from the cache world that could be applied here /@slightlylate@marcosc1 reply 0 retweets 0 likes -
Replying to @yoavweiss
@jaffathecake But we could start with some JS based "monitor" and work our way into native support from there /@slightlylate@marcosc1 reply 0 retweets 2 likes
@yoavweiss: that's why I prefer storage pressure events before anything else. Can already do most strategies.
/cc @jaffathecake @marcosc
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.