Nick, You said --- If you want to drive behavior, I'd rely on the client making requests based on the js callbacks for onclose and onerror.....Thanks for that tip. It has given me a gem of an idea.
You also said Channels only last about 20 minutes. I was under the impression that when you create a channel, you can specify a time limit up to 24 hours. Are you saying this is incorrect or this is for something else? On Friday, December 9, 2016 at 3:21:54 PM UTC-8, Nick wrote: > > Managing the connection on the client side is not as simple as the server. > The following may be useful: > > The dev server simulates channels by polling, so it isn't a great guide > for how it works in the live environment. > > Channels only last about 20 minutes. On the client, pull get the js error > callback, just establish a new connection and continue. If this seems to > have some issues, there are some hacks published to stack overflow that > seem to make reconnecting more reliable. > > Disconnect is mostly reliable, but it's probably only useful for cleaning > up data on the server. If you want to drive behavior, I'd rely on the > client making requests based on the js callbacks for onclose and onerror. > > Once you client side and server side code is bedded down it's very > reliable and robust. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/b5fefd36-e92c-4d00-bb94-20c935e92cd1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
