Kind of off topic, but can someone from google explain the Quota implications of the Channel API.
I see above there is considerable CPU associated with creating the socket. Can you provide more details around if we will be paying for all the requests the JS api makes to keep the socket open? Thanks. On Dec 5, 1:57 am, Moishe <[email protected]> wrote: > Latency should be generally significantly less than 500ms (that's not > a guarantee, but it's what I've been seeing in my end-to-end tests). > > Channelset-up time (the time between when you call > goog.appengine.Channel.open and when your socket.onopen callback gets > called) can be longer, sometimes up to 10 seconds or so. > > There are no reliability guarantees -- messages can be dropped or > delivered out of order, but that should be the exceptional case rather > than a normal case. If you have an application which _requires_ all > messages to be delivered (eg. you're sending deltas to some complex > data structure) you will need to add sequence numbers and checks > yourself (though please feel free to file a feature request about this > if you'd like). -- 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.
