<div class="gmail_quote">On Fri, Aug 21, 2009 at 11:10 AM, Aaron Boodman <span dir="ltr"><<a href="mailto:aa@google.com">aa@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Aug 21, 2009 at 4:50 AM, Mike Wilson<<a href="mailto:mikewse@hotmail.com">mikewse@hotmail.com</a>> wrote:<br>
> Another thing:<br>
><br>
> From the proposal it seems it will be possible for the GlobalScript context<br>
> to keep references to objects (DOM, JS data, etc) private to pages, and vice<br>
> versa possible for pages to keep references to GlobalScript objects. This<br>
> also opens up for a new way for independent pages finding and keeping<br>
> references to each other's objects if they are somehow registered in the<br>
> GlobalScript.<br>
><br>
> When reloading a page there is also the additional dimension of the<br>
> GlobalScript possibly holding references to objects both from the previous<br>
> and current incarnation of the Document. In a way it seems GlobalScript<br>
> usage will in practice merge the JS worlds of all participating pages,<br>
> potentially including those already navigated away from.<br>
><br>
> What are your thoughts on this?<br>
<br>
</div>Don't all of these problems already exist with window.open() and<br>
frames? Can the existing solutions not be reused?</blockquote><div><br></div><div>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.</div>
<div><br></div><div>Dmitry</div></div><br>