Sanjeev Singh
Why should I use AJAX?
By Sanjeev Singh in ASP.NET on Jan 14 2009
  • kelly gammons
    Feb, 2009 2

    If you need to provide end users with a richer Web interface that doesn't require entire pages to be reloaded each time they perform an action, then AJAX might fit the bill for you. By using AJAX, you can minimize full-page postback operations and update parts of a page instead as users click buttons and other controls. This provides your Web applications with more of a desktop-application feel.

    AJAX is all about JavaScript. It relies on a special object called XMLHttpRequest that's built into all major browsers (FireFox, IE, Safari, Opera, and so on). You use this object to send data to and from a server directly from a page. Data returned from a server can be updated in a page using Dynamic HTML (DHTML) techniques. Many frameworks such as the ASP.NET AJAX Extensions simplify using the XMLHttpRequest object and eliminate cross-browser issues that normally occur if you write all of the code on your own.

    Adding AJAX functionality into Web pages has many pros, but also comes with its own set of cons. AJAX relies heavily on JavaScript, which adds to the learning curve for developers new to client-side Web development. Several other technologies, such as Cascading Stylesheets (CSS) and the Document Object Model (DOM), often come into play, as well. In addition to the learning curve, additional complexities, such as security and debugging, can be factors. While cons certainly exist, the pros associated with AJAX cannot be denied. AJAX allows users more efficient access to data and allows data to be returned and displayed more quickly due to the ability to update a part of a page as opposed to the entire page.


    • 0


Most Popular Job Functions


MOST LIKED QUESTIONS