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

Re: [webworkers] SharedWorker and ApplicationCache

From: Michael Nordman <michaeln@google.com>
Date: Mon, 9 Nov 2009 10:13:17 -0800
Message-ID: <fa2eab050911091013q379ab65asccbad271636900af@mail.gmail.com>
To: Alexey Proskuryakov <ap@webkit.org>
Cc: Anne van Kesteren <annevk@opera.com>, Drew Wilson <atwilson@google.com>, WebApps WG <public-webapps@w3.org>
Shared workers do not depend on HTML documents for resource loading. I think
the webkit impl may have it cobbled together that way at the moment, but
thats per-happen-stance, not per-the-spec.

Shared workers effectively establish a new top-level-browsing-context all
unto themselves.

On Mon, Nov 9, 2009 at 10:09 AM, Alexey Proskuryakov <ap@webkit.org> wrote:

>
> 07.11.2009, в 10:47, Michael Nordman написал(а):
>
>
>  I've been wondering if SharedWorkers should have a means of establishing
>> an appcache similar to how pages can via the <html manifest='x'> mechanism.
>>
>> My mental model is that a shared worker is very much like a top-level page
>> with respect to appcaches, but that means for a shared worker to
>> express/establish its appcache is missing.
>>
>
> Don't shared workers depend on HTML documents for network loading? I'm not
> sure how they can have independent caches, if they just ask a document to
> fetch a resource for them.
>
> - WBR, Alexey Proskuryakov
>
>
Received on Monday, 9 November 2009 18:13:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:35 GMT