Ajax examples

Ajax allows for rich-internet applications that mimic the responsiveness and complex user interfaces typically associated with desktop applications. Moving applications to the web browser opens many possibilities, including the ability to save user data, connecting with other users for collaboration and sharing, and making deployment and using the application easier since web browsers are standard-issue with most computers regardless of operating system.

If you’re interested in expanding your understanding of Ajax techniques and practices, check out these 25 hand-picked Ajax articles and tutorials that outline various methods and concepts involved in the development of Ajax-based applications.

Please check out below link to get the 25 hand-picked Ajax articles and tutorials

http://sixrevisions.com/ajax/ajax_techniques/

JSON

JSON (JavaScript Object Notation) is a lightweight computer data interchange format. It is a text-based, human-readable format for representing simple data structures and associative arrays (called objects). The JSON format is specified in RFC 4627 by Douglas Crockford. The official Internet media type for JSON is application/json.

The JSON format is often used for transmitting structured data over a network connection in a process called serialization. Its main application is in Ajax web application programming, where it serves as an alternative to the traditional use of the XML format.

Although JSON was based on a subset of the JavaScript programming language and is commonly used with that language, it is considered to be a language-independent data format. Code for parsing and generating JSON data is readily available for a large variety of programming languages. The json.org website provides a comprehensive listing of existing JSON bindings, organized by language.

More and more Ajax developers are choosing JSON for their data
transfer instead of XML. Although XML has been the pillar of Ajax (X
is for XML), JSON has become the choice of most developers because it
was particularly built for JavaScript. Compared to XML, JSON is
lighter and will work faster compared to XML. This lightweight
function enables Ajax based websites and applications to run faster.

The reason why JSON is very efficient in data transmission is its
ability to function in itself. By this function we mean that JSON has
the ability to "EXECUTE" without the aid of other functions. XML is
only a format which will be used to transmit data and files, but JSON
is very effective in terms self execution.

More Information : http://www.json.org/

Microsoft Ajax Repeater Control

Apart from being used in complicated RIAs with colorful interfaces,
Ajax is also used for a more practical use such as data control and
interaction. There are functions that any developer could use to
display data in an Ajax way which does not only look good but has
efficient functions which could not be seen in HTML based sites.

It is relatively easy to build a repeater control. A repeater control
is a binding of XML, JavaScript and HTML codes that could get really
messy if you do not do it step by step. As we have previously pointed
out, Ajax repeater control is quite easy since you just have to create
an XML file and wrap it up with JS and HTML. But XML takes a lot of
line that when you integrate the whole webpage with the repeater in
it, you will never get to understand the whole webpage yourself.

Read More...
http://www.ajaxwith.com/Microsoft-Ajax-Repeater-Control.html

AJAX control --- Update Panel

The UpdatePanel is useful in situations where we only want a portion of the page to postback rather than the entire page. Such a limited postback is called a partial postback, and is easy to implement using the UpdatePanel.
Many ASP.NET controls can cause postbacks: Button controls, when clicked; DropDownLists and CheckBoxes, when their AutoPostBack property is set to True; and so on. Under normal circumstances, when these controls cause a postback, the entire page is posted back. All form field values are sent from the browser to the server. The server then re-renders the entire page and returns the complete HTML, which is then redisplayed by the browser.
When these controls appear in an UpdatePanel, however, a partial page postback is initiated instead. Only the form fields in the UpdatePanel are sent to the server. The server then re-renders the page, but only sends back the markup for those controls in the UpdatePanel. The client-side script that initiated the partial postback receives the partial markup results from the server and seamlessly updates the display in the browser with the returned values. Consequently, the UpdatePanel improves the reponsiveness of a page by reducing the amount of data exchanged between the client and the server and by "redrawing" only the portion of the screen that kicked off the partial page postback.
All of the GridView's rich functionality - paging, sorting, editing, and deleting - are accessible when its placed within an UpdatePanel without the need for any special code or instructions.
If GridView is in an UpdatePanel, actions that would normally cause a full postback - moving to the next page of data, sorting, editing, or deleting - instead result in a partial postback.