Hey, Dion posted on Ajaxian about this today http://ajaxian.com/archives/massively-parallel-crowd-sourced-javascript-app-server-seti-for-js
The App Engine service went down afterwards for most of day. I guess this cant really be fixed. The application is not really doing a lot of processing by itself, but it has to do some busy waiting for (using sleep) the JavaScript app servers to reply, so that some of the requests might take a while. It'd be nice if the quota could be increased, since, by design, the app isn't really supposed to ever actually use a lot of CPU (because processing is done on the app servers) Bye Malte On Sat, Dec 6, 2008 at 6:24 PM, Malte Ubl <[EMAIL PROTECTED]> 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 [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 -~----------~----~----~----~------~----~------~--~---
