Yes, though saving bandwidth != saving server resources.
I agree that AJAX integration is a good idea, but it can be a bad idea if not implemented just right.
The two major benefits of using AJAX should be:
- Make performing tasks easier and or faster for the user
- Result in a lighter server load
If it does not do either of those two, then AJAX is useless.
A decrease in Bandwidth is usually always a benefit of using AJAX, so then you’re really going to look for a savings in Server resources, or something that significantly helps the user perform a task before implementing AJAX.
abble CoSa NoStrA wrote:ajax isn't a difficult thing for accessibility?
The biggest change that I could see in resources, both bandwidth and server load, as well as user performing tasks would be to streamline confirmation boxes.
This would not require AJAX at all (though some people view it as an AJAX feature).
That is, basically you would enable the “Are you sure you want to perform this action? (Yes|No)” in a JS alert or in-page JS box, which would confirm the action before proceeding.
Then the information contained in the “You have successfully performed X action” would be displayed on the return to page
thus eliminating two steps and two page loads.
Again, this does not use AJAX, but would significantly improve the speed at which a task can be accomplished and save on bandwidth and a bit of server resources (2 fewer page loads/processing).
Side note, can a Moderator move this to 3.0 Discussions Forum?