Google I/O 2010 - Real-time apps w/ App Engine and Feed API
Why Stack Overflow recommends it
Stack Overflow users link it when answering questions about Comet, server push or WebSockets on Google App Engine, since it is the original session announcing the Channel API.
Recommended by 1 people across 1 different months, 2010 to 2011.
What it is
A Google I/O 2010 session by Brett Bavar and Moishe Lettvin introducing the App Engine Channel API and Feed API v2 with PubSubHubbub push updates. It explains how to push data from an App Engine app to a user's browser for real-time web apps.
What people said
Recommends systempuntoout · 2010-11 · Stack Overflow · on “how can i create a websocket on google app engine for html5”
I think you should wait for Channel API . Channel API - The Channel API lets you build applications that can push content directly to your user’s browser (aka “Comet”). No more polling for updates! this is already part of the SDK but does not work in production. Here [this video] a video that show this new upcoming feature Here [LINK] a demo application with a multiplayer trivia-quiz EDIT: available with SDK 1.4.0 [LINK]
Cites Moishe Lettvin · 2010-05 · Stack Overflow · on “Implement Comet / Server push in Google App Engine in Python”
We just announced the Channel API to do comet push with App Engine apps: [LINK] If you're at Google IO, I'll be talking about this at 1pm tomorrow (on the APIs track): [LINK] Here's the YouTube video of the session: [this video] Hopefully last update! This is now released: [LINK]
Cites Drew Sears · 2010-07 · Stack Overflow · on “How will http server handle html5 web sockets?”
Bi-directional communication between web servers and browsers is nothing new. Stack Overflow does it today if a new answer is posted to a question you're reading. There are a few different strategies for implementing socket-style behavior using existing technologies: AJAX short polling: Connect to the server and ask if there are any new messages. If not, disconnect immediately and ask again after a short interval. This is useful when you don't want to leave a lot of long-running, idle connections open to the server, but it means that you will only receive new messages as fast as your polling interval, and you incur the overhead of establishing a new HTTP connection every time you poll. AJAX
Cites Tiwari · 2011-01 · Stack Overflow · on “Google app engine Channel API for COMET on non Javascript clients”
Cool,... I found an X-Ray view of "channel api" on the app engine talk og Google I/O [this video] It uses hidden Iframe [LINK] Now i will try to imitate th client in python or something.