On Sat, Nov 21, 2009 at 12:26 PM, John Tamplin <[email protected]> wrote:
> On Sat, Nov 21, 2009 at 12:02 PM, Scott Blum <[email protected]> wrote: > >> BTW: I was thinking about this later, and was thinking it might be nice to >> do two additional things to this: >> >> 1) Make the guts of the disconnect logic occur in a timeout, to avoid any >> "what's higher up on the stack that's going to execute after me" issues. >> > > That might be hard to do on all the platforms, though the > __gwt_disconnected method could do that itself pretty easily. > I actually meant we should set the timeout from within the __gwt_disconnected() function. IE, make the JS to more work to make the plugins simpler. > > >> 2) Make the call a one-shot in the JS code; replace the disconnect >> function with an empty function, so that if a plugin calls it multiple times >> it won't do anything on subsequent calls. >> > > The plugin already stores a connected state, so I would expect this to get > called only on transition from connected->disconnected, so I don't think > that would be useful. > Makes sense, just seemed like a useful defense mechanism. Scott -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
