W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2009

Re: [webworkers] SharedWorker and ApplicationCache

From: Drew Wilson <atwilson@google.com>
Date: Sat, 7 Nov 2009 09:14:19 -0800
Message-ID: <f965ae410911070914g4f43ca8dm857c82e4d03a7ffe@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: WebApps WG <public-webapps@w3.org>
You may have two separate pages running from different app caches (or
version), each of which is trying to access the same shared worker, so we
don't want to tie it explicitly to a specific parent's app cache/version.

It does seem a bit wonky, though - if you have one parent who has an app
cache that has two resources in it (a.js and b.js) and another parent who
has an app cache that has a different two resources in it (a.js and c.js),
it's non-deterministic which app cache the shared worker would be associated
with, and this could break apps.

I'm not sure that there's a good solution for this, given that manifests can
only be associated with an HTML resource.


On Sat, Nov 7, 2009 at 8:57 AM, Anne van Kesteren <annevk@opera.com> wrote:

> We were wondering why there is a quite complicated resolution algorithm to
> determine the ApplicationCache that belongs to the SharedWorker rather than
> just passing the ApplicationCache to the SharedWorker at creation time (i.e.
> as constructor argument). Is there anything that is gained by the current
> model?
> --
> Anne van Kesteren
> http://annevankesteren.nl/
Received on Saturday, 7 November 2009 18:14:17 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:20 UTC