[webkit-dev] SharedWorker design doc

Drew Wilson atwilson at google.com
Sun Apr 19 10:42:03 PDT 2009

Those are good questions - I've been primarily concentrating on the
mechanisms around worker lifecycle management so I'm not entirely up to
speed on the loadng mechanisms. The resource loading issues for dedicated
Workers are the same as for SharedWorkers, since dedicated Workers can
outlive their parent window closes once we support passing MessagePorts
through Worker.postMessage().
I know that David Levin has been doing work on enabling loading within
workers - I've CC'd him in hopes he might have some insights here.


2009/4/18 Alexey Proskuryakov <ap at webkit.org>

> Hi Drew,
> Thanks for the detailed proposal, it's great to have one.
> Prior to diving into threading details, I'd like to clarify a background
> assumption that doesn't seem to be mentioned in the proposal. How does a
> SharedWorker relate to the browsing context that created it? Specifically,
> we probably don't want a SharedWorker to be a top browsing context, because
> that would be an easy way to subvert same origin cookie policy. And since
> loading in WebCore can only happen when there is a Frame, what will happen
> to a SharedWorker whose original frame goes away?
> 18.04.2009, в 8:55, Drew Wilson написал(а):
>  Any feedback would be appreciated, especially for some of the
>> cross-threading and worker lifecycle issues.
> - WBR, Alexey Proskuryakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20090419/9c162fe8/attachment.html>

More information about the webkit-dev mailing list