[webkit-dev] GlobalScript in WebKit
darin at chromium.org
Mon Nov 30 16:05:50 PST 2009
On Mon, Nov 30, 2009 at 3:08 PM, Geoffrey Garen <ggaren at apple.com> wrote:
> > Just a note:
> > In Chrome, a SharedWorker is reachable from any WebKit process, whereas a
> SharedScript would only be reachable within a WebKit process. This is an
> interesting distinction, and I can imagine some use cases for SharedWorker
> that SharedScript could not address. (This distinction arises because we
> did not want to build a script proxy between WebKit processes as that would
> be quite costly.)
> > For example, suppose you wanted to have only one instance of a web app
> responsible for manipulating a database or communicating with a server.
> There's no guarantee that multiple instances of a web app would all run in
> the same WebKit process.
> Actually, I objected to that distinction, and it has been removed from the
> You can find the discussion here:
> And the specification here:
It is not clear to me what you are arguing for. Are you saying that Chrome
is wrong to allow *unrelated* similar-origin-browsing-contexts to see the
same SharedWorker instances?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev