Hey, as an update to this post, I have a developed a new service based on app engine that makes every client addressable through URIs.
By including a piece of JavaScript in your page you receive an URL which can be used to make HTTP-GET-requests to the client. This enables comet-style applications without any special provisions on the server. If the client has Gears installed there will only be one comet-connection per client no matter how many websites are using the service and how many windows are open. If Gears is not installed only one connection per domain is made (independent of the number of open windows). More info and a demo is here: http://joose-js.blogspot.com/2008/12/universalcomet-making-every-client.html Cheers, Malte On Sat, Dec 6, 2008 at 6:24 PM, Malte Ubl <malte....@gmail.com> wrote: > Hey, > > just wanted to let you guys know about a small project/experiment of > mine that you might find interesting. I created a sort of application > server that runs within Google Gears workers which have a pseudo > persistent connection to an App Engine application. Clients can send > http requests to the App Engine app which are then delegated to the > application servers on clients running the Gears application. In a > (twisted) way this also enables writing parts of App Engine > applications in JavaScript. > > More info is here: > http://joose-js.blogspot.com/2008/12/massively-parallel-crowd-sourced.html > > Cheers, > > Malte > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---