Web applications commonly exchange information between the client (the browser) and the server (the ASP.NET application). In traditional web applications, this communication
is usually insinuated when the visitor submits a form. This prompts the browser to re-request the page, sending the values of the form's inputs through the HTTP POST header.
The server then renders the page and returns the entire page's markup, which is then redisplayed. AJAX-enabled web applications streamline this process. Instead of synchronous,
only the part of the screen whose contents have been modified (rather than redrawing the entire page, as with a full page postback).
Transmitting information over the Internet requires the sender to serialize it into some string-based format prior to sending it, and the receiver to deserialize it back into
an object state that it can work with. For instance, if the client wants to send an array of integers to the server it must convert that array from its in-memory representation
into a string, so that it can be transmitted across the network. Likewise, upon receiving the request, the receiver must turn that string representation of an array of integers
back into an array of integers, so that it can use it programmatically.
XML was designed to serialize complex data into a string-based format, and early AJAX frameworks used XML as the serialization format. However, modern AJAX implementations use
both human-readable and platform independent. It differs from XML in three important ways: it is much simpler to understand and implement than XML; it is less verbose,
This article provides an overview of JSON's rules and illustrates how it is used in AJAX-enabled web applications. We'll also look at using the Microsoft
ASP.NET AJAX framework's
in C# or Visual Basic code on the server. Read on to learn more!
Read More >