W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2010

[Bug 11548] Suggestion for improved caching functionality in html5 specification

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Dec 2010 15:58:59 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1PSXHH-0005W5-MR@jessica.w3.org>

Tab Atkins Jr. <jackalmage@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |jackalmage@gmail.com

--- Comment #1 from Tab Atkins Jr. <jackalmage@gmail.com> 2010-12-14 15:58:59 UTC ---
(In reply to comment #0)
> Essentially, the lack of an api call along the lines of .add_to_cache(url,
> expires) seems like a glaring omission and means that I can't (for example)
> have some javascript dynamically generate links to images and have those images
> cached locally.

There are many ways to force a caching opportunity.  For example, you could
just create a bunch of images in javascript.  You don't need to add them to the
document, just create them and set their src.  They'll be downloaded and cached
as appropriate.  You can do this with *any* GETable resource, not just images.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 14 December 2010 15:59:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:35 UTC