How quick is delivering a message through Channels API

[Andrius]

Hi guys,

I have an app which does ajax request every second to get data from
the server and display in the browser.
My question is how quickly messages are delivered through Channels API
to the client? Does anyone measure the latency? Will it deliver
messages faster than doing ajax request every second?

Would be grateful for you knowledge.

Thx,
Andrius

[Max]

According to this talk, the latency should be no worse than pulling at any frequency rate

http://www.google.com/events/io/2010/sessions/building-real-time-apps-app-engine-feed-api.html

In practice, we use channel API in project Yaac (http://code.google.com/p/yaac/) to push back query results piece by piece and it works quite good, the latency is just neglectable

[Andrius A]

Thank you Max

--
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/-/q_yE5v7SAjgJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Strom]

Certainly faster than a second.

[Kroc]

I've swiched from pulling to channel without problem.

Like Max say, latency is neglectable. It also save bandwith and cpu time.

Still a little billing issue: channel are cheap but free quota is only 100 opened chanels per days. In my case I'm going to pay the 9$ only for channels.

[Pascal Patry]

My initial tests on Channels showed that a small latency exists, but
it's only when establishing the connection. For instance, in the
_ah/connected handler, if you send a message as soon as the connection
opens, that message will be received with a latency of around 1 second.
However, next messages are a lot quicker to be transmitted.