Extending the cloud to the client with Gears and App Engine

[Malte Ubl]

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

[Xavier Mathews]

Post This over in gears also.

--
Xavier A. Mathews
Student/Browser Specialist/Developer/Web-Master
Google Group Client Based Tech Support Specialist
Hazel Crest Illinois
xavier...@gmail.com¥xavier...@hotmail.com¥trues...@yahoo.com
"Fear of a name, only increases fear of the thing itself."

[Xavier Mathews]

nvm i c u did.

[Malte Ubl]

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

[Marzia Niccolai]

Hi Malte,

This is very cool.  If you are having issues with the quota, please apply to have your quota increased:

http://code.google.com/support/bin/request.py?contact_type=AppEngineContact

-Marzia

[kang]

good job...it's cool

--
Stay hungry,Stay foolish.

[Malte Ubl]

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 <malt...@gmail.com> wrote: