channel-api

Hopefully Moishe sees this: in development mode, the channel api client (javascript) resorts to polling... and uses a very fast polling rate. After poking around I found that if I set goog.appengine.Socket.POLLING_TIMEOUT_MS = interval; I can control the polling rate. What I'm wondering is: How do I know if/when the client is going to go into "poll mode" in production? Is it possible to force the client into "poll mode"? What happens if I reach the channel quota for my app? will the /_ah/channel/ endpoint just stop working altogether? or will it resort to polling? -Thank you Answers: The

I am trying to learn GAE's channel API (using Java), but I cannot figure out where to start from. I went through Channel API Overview (Java) but the code posted there wasn't complete for brevity purposes. And since I m newbie, it would be very helpful if complete example code is available. Thanks, Shrey Jon Newmuis The code in the Channel API Overview that you've linked to is pretty complete, it's just a bit all over the place. I will admit, once you understand it, I feel like it's much simpler than how they've made it seem, but I'm glad they erred on the side of providing too much information

How can I implement Comet / Server push in Google App Engine in Python? Moishe Lettvin We just announced the Channel API to do comet push with App Engine apps: http://googleappengine.blogspot.com/2010/05/app-engine-at-google-io-2010.html If you're at Google IO, I'll be talking about this at 1pm tomorrow (on the APIs track): http://code.google.com/events/io/2010/sessions/building-real-time-apps-app-engine-feed-api.html Here's the YouTube video of the session: http://www.youtube.com/watch?v=oMXe-xK0BWA Hopefully last update! This is now released: code.google.com/appengine/docs/python/channel At

It seems the only way to make the GAE Channel API financially viable is to implement some kind of pooling mechanism (one of the senior app engine product managers even told me this when I emailed them about the exorbitant price) to reuse channels that have not yet expired. I've been brainstorming ways (places) to implement a channel pool, but each method I think of has some pretty serious drawbacks. Static memory of a Servlet -- Good, but will drop quite a bit of open channels when a new VM instance opens and/or a client gets passed from one VM to another. Memcache -- At least the memory is

I have built a social network/dating type application on the AppEngine and am currently in the process of adding a chat built on top of the Channel API. However, the problem that I have is that users may reload or navigate to new pages while the chat is going on (as they can in Facebook). This means that the server doesn't easily know if it should generate a new channel ID token for a given client, or if a given client has already been assigned a channel token. It would be extremely useful if there were a way to check (server side) if a particular client already has a channel open. For example