> 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.
What you seem to be implying is that a "SharedScript" would not actually achieve the one thing it is intended to gain -- a common context for all instances of a page. > > -Darin --Oliver > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
