O’Reilly: Inside RIA

So continuing on with my discussion with Jaxer, the new product from Aptana, today I got my hands a bit dirty with the code. I've complained previously about the lack of documentation, so please bear in mind that any code sample I show will probably not be 'best practice' - but since there isn't any best practices doc, I can't be wrong, right? (Of course, by the time I post this, I bet there will be one.)

Late last week I discussed the launch of Jaxer by Aptana. Jaxer's idea is simple. Take the same JavaScript knowledge you use in building rich internet applications and apply them to the server side as well. I've taken some time to play more with Jaxer and I'd like to show some of what I've learned so far.

I just read about this a few minutes ago, so forgive me if this is old news, but it looks like Aptana has launched Jaxer. In their own words, this is: Modern web sites and applications use Ajax to create engaging user experiences: the HTML and CSS are set in motion using JavaScript running in the browser and calling back the server. To achieve this, the server needs to prepare the web page appropriately, and to know what to do when the JavaScript calls it. But the server knows nothing about the HTML and CSS DOM, nor how to handle JavaScript data, and you can't code it in JavaScript...