On Mon, Nov 30, 2009 at 3:08 PM, Geoffrey Garen <gga...@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 > specification. > > You can find the discussion here: > https://bugs.webkit.org/show_bug.cgi?id=31317. > > And the specification here: > http://docs.google.com/View?id=dxv3cth_4gvggh3gh. > > 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? -Darin
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
