Re: Support for page/resource size

On Wed, Aug 13, 2014 at 6:32 AM, <> wrote:

> This is not a Chromium bug. It’s a side effect of the fix I made to this
> issue: In a
> nutshell, I had to change the Resource::Type of the LINK rel=subresource
> request to be the type that would eventually be needed in rendering the
> page in order to fix the problem of de-duping not working in the renderer’s
> memory cache. My assumption is that the design work you are doing on
> preload hints will change the way this is implemented so I’m not going to
> worry about this issue for now.

Gotcha, sg.

> As far as how we can determine that a preloaded or pre-rendered object is
> used, any thoughts on my proposal below about indicating when an object
> comes from the “ephemeral cache”?

I think that's too implementation specific, which brings us back to
defining "matched". Opened a bug to track the discussion:

Received on Wednesday, 13 August 2014 18:51:31 UTC