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.)

I took some time to look over the Architecture Review. Jaxer works much like ColdFusion (and other server side languages), where the Jaxer server will preprocess your code before returning it to the browser. Along with removing any server side code, Jaxer will add JavaScript code to your response to help enable it's basic feature sets. Read the review for more details.

How about what Jaxer supports on the server side? The docs say database access is supported (SQLite and MySQL), file access is supported, and network access. "Network Access" is a bit vague. It sounds like it could support POP or SMTP, but that the code would have to be written yourself.