Note that, in spite of the name, you don't have to use xml with AJAX. I use the combination of an AJAX front end on a web page to invoke rev cgi scripts on the server in order to update a section of the page. Works fine without any actual xml involved. I prefer to call it AJAR.
I have never seen a well-scaled app that worked this way. There has, in my experience been too much traffic back and forth to make it efficient. It isn't that the server can't handle the load, but generally the clients can't.
That said, you're spot on about the hardest part being "accurately representing what you want your application to do". And that's true for any app, not just restricted to AJAX.
What makes this harder, though, is the fact that you are taking an application that is already written and essentially converting it to something else. That, I think is the hard part, because you are asking the machine to do it. -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
