Re: [whatwg/fetch] Define the "Preload Cache" (#590)

I agree that the "preload cache" doesn't need an eviction policy, size limits, etc.

I'm not sure I see the benefits of defining that cache above Fetch. It seems like it would significantly increase the room for mistakes on the part of the different Fetch callers.

I'm similarly not sure we need to evict preloads from the cache if their corresponding `<link>` is removed. I don't think this is what current implementations do. What's the use case this will enable?

Also, I think it's worthwhile to also think of generalizing the "list of available images" from HTML as a generic cache for all resource types, which is how it's implemented in at least 2 engines. While I wouldn't want to couple both efforts, it'd be good to have a holistic high-level design to how they'd both work. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/590#issuecomment-925609125