[Bug 20677] Unable to detect whether a file is in cache or not

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20677

--- Comment #2 from François REMY <francois.remy.dev@outlook.com> ---
OK, I'm going to create a duplicate. It would be easier if we could report a
bug to more than one component at the same time, but I didn't see this option
anywhere. Annoying if you want my opinion.

Now, let's answer to your question. 

In the first case, the image could have been downloaded using <image
src="abc-123.png" srcset="2x abc-123.2x.png" /> if the browser was first
launched on a 'retina' screen. You have no control on whether the browser will
choose the first or the second one, but if later on you want to use the exact
same image on the same device on a canvas, you want to use whatever version was
already downloaded.

In the second case, the dictionary may have been cached because the user
accepted to use an appcache for the synonymous webservice (which involves
caching the dict). However, you don't want to use the file if it was not cached
because it's probably way to huge to be used for just one lookup.

In the last case, I already explained why some files may be in cache: the
appcache is minimalist by default but may be growing at the user request to
include more components. As you want to add more components in the appcache,
you may want to know which files are already cached. Some files may also have
been downloaded without being in the appcache on per-use basis. With a bit of
luck, they may still been in the cache and will not need to be reused.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 15 January 2013 20:16:12 UTC