This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Bug 17974 note 4's use case seems best handled by adding a simple API to applicationCache for adding and removing extra files: applicationCache.addExtra(url); applicationCache.removeExtra(url); applicationCache.getExtras(function (files) { ... }); ...where the callback to getExtras() gets an array of URLs.
*** Bug 17974 has been marked as a duplicate of this bug. ***
*** Bug 11548 has been marked as a duplicate of this bug. ***
*** Bug 10263 has been marked as a duplicate of this bug. ***
*** Bug 21297 has been marked as a duplicate of this bug. ***
Not Found The requested URL /bugzilla_public/docs/en/html/query.html was not found on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. siempre llego a algo parecido a esto de arriba. el problema fue creado por los señores que iniciaron las organizaciones que autorizan las asignaciones de identificadores especificos de usuarios en internet. todo esto en acuerdo comun con los servidores de internet locales, gobierno y todo lo que conecta, en el manejo de servicios que se relacionan; que han armado un bloqueo, que todo mundo conoce; y que los arbitros estan a favor de ellos.
The proposed API addExtra() etc reflects an intention that may not pan out in actual use: That this would be used for secondary resources, not primary cached assets. The fact may be that for many applications, an API like this would be the primary way to define the cache. In fact, they may define no manifest at all and ONLY define resources on the fly. The language of the methods should reflect that with a term other than "extra". Also, this fails to provide a way to introspect the non-dynamically added resources, which may also be useful. "What assets does my current cache provide me?" code might want to ask.
This is probably going to end up handled by ServiceWorkers instead.
(In reply to francisco alejandro viana canizalez from comment #5) > Not Found > > The requested URL /bugzilla_public/docs/en/html/query.html was not found on > this server. > > Additionally, a 403 Forbidden error was encountered while trying to use an > ErrorDocument to handle the request. > > siempre llego a algo parecido a esto de arriba. > > el problema fue creado por los señores que iniciaron las organizaciones que > autorizan las asignaciones de identificadores especificos de usuarios en > internet. todo esto en acuerdo comun con los servidores de internet locales, > gobierno y todo lo que conecta, en el manejo de servicios que se relacionan; > que han armado un bloqueo, que todo mundo conoce; y que los arbitros estan a > favor de ellos.
I'm punting on this. ServiceWorkers are going to do this.