I know your concerns as I've recently had lots of thoughts on client-server-ajax-comet-websockets state of the art. While your matrix seems quite radical, it's

I know your concerns as I've recently had lots of thoughts on client-server-ajax-comet-websockets state of the art. While your matrix seems quite radical, it's interesting approach. You may find other approaches attractive as well. For example Zed Shaw's Tir is making an webapp flow looking procedural by smart using coroutines underneath. While the idea was invented before, I like his implementation; i didn't yet hack anything serious in it though. If you like evented style, Nitrogen is also very interesting. It allows you to program callbacks which jump from server to client and back in a clean way, IMO. That'll work for you if you can swallow Erlang syntax of course. I'd say this product is really production ready, btw.