Sorry for the late reply. You were right. The token I was sending was incorrect, so I can now reconnect after getting the 400.
I also added code to remove the iframe on socket close and that seems to be working as well. Thanks for your help Moishe! My app is almost ready for production and the Channel API has drastically improved the functionality. Thanks for all your hard work on this. On Jan 14, 11:26 am, Moishe <[email protected]> wrote: > Theerroryou're getting makes me think that the token you're passing > to your newChannelobject isn't valid. Can you add debug code and > verify that it's the same string the first time you create theChannel > & Socket as well as the second time? > > Also: if you're not getting an onclose message when you get the > onerror, you could try manually deleting the iframe named wcs-iframe > before creating the newchanneland opening the socket. (socket.close > is NYI in production right now, but the next version that rolls out to > prod - in a week or so - will have this fixed so you'll be able to > just call socket.close() in this case instead of messing with the DOM > directly) > > Hope that helps! > > -Moishe -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
