Re: [w3c/ServiceWorker] safari fetches from memory cache instead of Service worker (#1510)

@wanderview  I read those, but still, there's some vague statements. Have you found out the final answers? I will quickly ask my question in a simple way.

1) Which cache is the first one that browser goes to? I think It's memory cache overally.  Agree? but if i use service worker and if browser goes first to memory cache, it proves that my service worker is not in full control of my assets and that's a bad thing. It should be in control. What do you think?

2) I read this on that another discussion:
`So we do actually re-use our image cache across documents, but we explicitly disable that when service workers are in play.` 

I believe there're some kind of memory caches for js/css files too. But what you're saying is if service worker is in play, files don't get fetched from memory cache right?

3) In safari, this is all strange, because `first refresh` gives you assets from service worker and second refresh and all subsequent requests give you from memory cache. So, it's interesting why this is the behaviour. Using service worker should mean that it's in full control of assets , but somehow memory cache makes it all weird. What would you say?



-- 
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/ServiceWorker/issues/1510#issuecomment-609073953