A Google search came by my site the other day for the following query: "ajax definition .net for dummies"
Firstly I will provide a breif definition of what AJAX is:
Asynchronous
JAvaScript and
XML. Using an enhancement (originally by Microsoft for Web Outlook) in JavaScript that allows Web pages to be more interactive by communicating with the server retrieving data without the browser reloading the entire page.
This communication helps provide a better User experience when interacting with a website (when used correctly). Originally the browser had to reload the entire page before being able to show updates to the page.
Now that the definintion is given, I will talk
briefly about using it in .Net.
ASP.Net really was designed for the old method of working. A page would be requested, events internally would fire based off the logic in the page and the Result would be displayed. Ajax really isn't like this, Ajax says, I already have the page, but I need to update this small portion of the page. Nativly, ASP.Net (1.x) can't handle this, it wants to load the page in its entirity.
All is not lost, because the Request Pipeline in ASP.Net is so flexible and has the ability to allow plugins to handle the incomming HTTP Request, people have developed plugins (or HTTPHandlers) that enable the developers to handle the AJAX Requests. The general consensus seems to be that Ajax Methods are embedded in the page, and the HTTPHandler pulls out the single method it needs to execute and only runs that code.
Some .Net Based Ajax Frameworks are:
