According to these urls "maintaining security in ajax applications is a tedious task" which bothers developers who is conducting the transition.
"Tedious"? That seems a curious attitude. It is a crucial task for all web apps, and the frequent use of XMLHttpRequest (which underlies AJAX) increases the HTTP surface of a web app, adding some new attack vectors. You may wish to work through a book like Ajax Security to learn more about that.
Sorry for excavating this old post, but I don't understand it.
In the context of Ajaxifying an nonajax based web application were the following for consequences off the following aspects asked:
- Page navigability
- Browser compatibility
The other two points page navigability and Scalability weren't answered, or at least I didn't have seen them. My understanding of page navigability is that this area describes how my web pages are linked together and how I can navigate from one page to another. Due to the possibility with Ajax to load smaller parts of information to a page, I would say that it make also sense to reevalute this point.
From a scalability point of view it is clear for me that much more (smaller) requests will be send to the server than earlier the fewer (bigger) requests. Depending on the browser based events that trigger an Ajax-request I would also see the scalability as an important point.
It would be great if someone could share his thoughts.
It depends on how your using ajax. If you are going to change your whole application to a restful service/json ajax model, then I'd say you are starting from scratch. If you want to start bringing in partial pages instead of full pages then its more like you are just breaking up your current application into smaller pieces.
Ew. You guys are ugly with a capital UG. Here, maybe this tiny ad can help:
a bit of art, as a gift, that will fit in a stocking