The SDK provides a javascript lib for the client side (which simulate websocket). But the client can't write into the socket, and need to call serverside thru ajax ;-(. Only the server side can write into it to push data for clients. APIs are low level, server side needs to maintain its clients, thru datastore.

I can start to implement web game in atomic bombers

EDIT : It seems it's not real websocket (to be able to work on every browsers, or because html5 specs is not really finnished). But it works like. Currently the JS SDK do polling for you ;-(. Hope the real websocket will be available soon !

Now, it's over ;-) I had switched to my own, which is a app engine website, which works online and offline, and sync enabled (thanks to newest html5 features). No need to say that it fits my needs. My snippets will always be available, at least, for me ;-) ... There is now a "snippets link" at the bottom of my website.

I don't know if I will get the force to make it available for everyone too. But it's perfect for me.

Try theses experiments in compatible browsers, or this wonderful NES emulator in full javascript ... Everything seems possible : quake2 in html5 browsers !

Websocket, webworkers and offline features are others great html5 features, to be able to replace flash ! (others html5 features on html5demos)

I play a lot with websockets in eventlet, but nothing to present here, because I'm waiting for the GAE support ;-) (don't want to setup an external websocket server). But it's really amazing to be able to communicate in the 2 ways !

I've made a little game : cavepilot using canvas (my record is 44seconds, and yours ?)! In the future, I'd like to make it two players with websocket support.

And a fun thing to make orbits !!!

The other great feature is the app's delete. But I will never use it ;-)

In the past few days, I updated the code to let it works with XMPP too (thanks to new xmpp service on GAE). And for the fun, I'd added a http frontend too ;-). Since that, I've made some enhancements to add more commands (WakeOnLan, todo backends, ...), and let it looks like a real good robot.

And now : I can talk to my website (this one), by Email, by XMPP and by HTTP, using this same robot ;-)

In the future, always for the fun, I think I will add a twitter and a google wave backend. It's really interesting ;-)

For now, it uses the jbrout news from my main website. So news are only available in "english". But, in the near future, french's news will be available too. You can subscribe to jbrout rss (french rss in the future), to stay tuned.

BTW, flux.manatlan.com was a subdomain of my old appspot-id (it was very dependant on this website). Now it has its own appspot-id and works alone (with its own cron, taskqueue, and own quotas). It's in beta stage now (use at your own risks).

So, this is the first post (a test ;-)) on my new appspot-id.

A cron job will invoke a URL at a given time of day. A URL invoked by cron is subject to the same limits and quotas as a normal HTTP request, including the request time limit.

An application can have up to 20 scheduled tasks.

And better, it was done like in my dream ;-)

Btw, GAE is one year old (happy birthday !), and is now java compliant.

In fact, I always used 10% of webpy. Webpy, although it was an anti-framework, is now a full featured framework (providing templates, sql access, form generator, markdown access, openid, session ...) Too much for me.

I'd got many troubles during the 0.2->0.3 phase (troubles with notfound/internalerror, markdown broken, reloader broken, seeother/redirect broken, https detection broken, ...). But I learned a lot of things hacking webpy during this phase.

Webapp is a simple thing, and miss some features, like simple cookies, routes according host, .... Webapp use the WebOb thing (for its request/response object), which is a really nice and mature library. The Do-It-Yourself from its author gave me the idea to do it my self. Nearly everything I needed were already here in webapp/webob, I'd just made a wrapper around webapp to offer some simple things, and aeweb was born.

And better: aeweb can be run outside of GAE, but you will need webapp and webob (But it was not its main goal)

Now, my main website (this one), is completly webpy free. The main problem was to remove templetor (the webpy template engine), to use tempita instead (which seems to be 10 times faster).