[whatwg] Global Script proposal.

Dmitry Titov dimich at chromium.org
Fri Aug 21 11:36:32 PDT 2009

On Fri, Aug 21, 2009 at 11:10 AM, Aaron Boodman <aa at google.com> wrote:

> On Fri, Aug 21, 2009 at 4:50 AM, Mike Wilson<mikewse at hotmail.com> wrote:
> > Another thing:
> >
> > From the proposal it seems it will be possible for the GlobalScript
> context
> > to keep references to objects (DOM, JS data, etc) private to pages, and
> vice
> > versa possible for pages to keep references to GlobalScript objects. This
> > also opens up for a new way for independent pages finding and keeping
> > references to each other's objects if they are somehow registered in the
> > GlobalScript.
> >
> > When reloading a page there is also the additional dimension of the
> > GlobalScript possibly holding references to objects both from the
> previous
> > and current incarnation of the Document. In a way it seems GlobalScript
> > usage will in practice merge the JS worlds of all participating pages,
> > potentially including those already navigated away from.
> >
> > What are your thoughts on this?
> Don't all of these problems already exist with window.open() and
> frames? Can the existing solutions not be reused?

It does look similar, so same methods could be used. One idea which was
mentioned (and seems like nice to have) is to have a couple of events
exposed to the GlobalScript global scope, 'connected' and 'disconnected'
which would fire when a page connects to a GlobalScript and right after it
is closed (so it 'disconnects' from it). This can help with housekeeping,
although more thought should go into defining those, their parameters etc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090821/26ac479a/attachment-0002.htm>

More information about the whatwg mailing list