I've seen problems with the Channel API where both sides of the connection were "half open", i.e. each side believed there was a connection but messages would not be sent.
I eventually replaced the Channel API with a node.js service running WebSockets. The GAE app posts messages to this service using URLFetch. It has worked really well so far, with only one outage incident (which was my own fault) and none of the issues with intermittent connectivity that I was seeing with Channel. - Kris On Sunday, December 30, 2012 12:00:42 PM UTC-8, [email protected] wrote: > > I've recently faced the problem. I've implemented some collaborative work > on my app. I've used the Channel API and it works really fine on localhost. > After deploy, the "update" in the other client is never received. why? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/Mnu2Bm-mAPAJ. 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.
