Keeping references around and explicitly closing didn't help.  My
first try at it caused a loop b/c calling the close causes the onclose
method to run which causes the setup function to run, etc.  Good
times.

Right now, removing the iframe is the way to go for me.

On Dec 30 2010, 10:39 pm, songs <coca.c...@gmail.com> wrote:
> Nope, it doesn't reload the jsapi source files again.
>
> I don't keep a reference of the channel around to close.  I figured
> since the onclose method was getting called the other close stuff was
> happening, too.  I'll try that approach when I get a chance.
>
> On Dec 30, 10:28 pm, Tim <meer...@gmail.com> wrote:
>
>
>
>
>
>
>
> > On Friday, December 31, 2010 4:08:16 PM UTC+11, songs wrote:
>
> > > Yay!  Removing the iframe before creating the new channel works.
> > > Hacky, but gets the job done and not too too dirty.
>
> > Just to check (and I hope I'm not jumping to conclusions again) but your
> > setupChannel() - it doesn't reload the /_ah/channel/jsapi source files again
> > does it ?
>
> > You should just be able to call
>
> >   channel = new goog.appengine.Channel( newChannelId );
> >   socket = channel.open();
>
> > again (I explicitly call socket.close() on the old socket and then set the
> > vars for the socket and the channel to null to be sure, but that's cos I'm
> > an old C++ hacker and still like to see at least a nod towards matching the
> > explicit creation and removal of resources).
>
> > --
> > T

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to