It is a very interesting concept. You could set up a public server for people to connect "alert bots" from app engine to client apps so we don't have to do the plumbing. Just send a signal from app engine to the proxy and then relaying it to the client.
>From GAE/myapp call yourproxy.com/myalertbot yourproxy broadcasts a signal to every client listening to myalertbot every client listening to ws:yourproxy.com can now go to GAE/myapp to get more data For example, say I publish a new entry on my GAE/blog, it then sends a signal to your public proxy which relays it to every client so they can come get the entry. Just a thought while we get websockets support in GAE On Dec 24, 10:07 am, Takashi Matsuo <[email protected]> wrote: > Hi, > > Let me share my trial implementation with > you.http://takashi-matsuo.blogspot.com/2009/12/integrating-websockets-wit... > > Recently, not quite a few people asked about how to use websockets on > appengine. IMHO, current appengine itself is not so suitable for > those architecture(pseudo server push) because of its 30 seconds > request limit. So, I tried it with an external websockets server. > > Could anyone tell me what do you think? > > TIA > > -- > Takashi Matsuo > Kay's daddy -- 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.
