HTML and CSS Reference
In-Depth Information
Client/Server Model
There are both a server and client components to consider when building a web application. On the server, IIS
responds to the HTTP requests as I mentioned. For static content, the HTML files can be simply stored in a virtual
folder within IIS and no programming is required. For dynamic content, a web application is needed to generate
ASP.NET allows you to write code to dynamically create HTML. For example, the page can query a database
and populate a grid using the data returned from the database. Likewise, the data presented in an HTTP Post
request can be written to a database. Also, while a web application is generally considered stateless, ASP.NET
provides several techniques for saving information between requests.
On the client side, the browser is responsible for rendering the content. This content is provided as HTML,
which is essentially text with embedded formatting tags. In addition, cascading style sheets (CSS) are provided
which instruct the browser how to format the content. The support for these HTML tags and CSS constructs will
vary, however, between the available browsers and herein lies some of the biggest challenges of web development.
Improving the Web Experience
The page-centric approach is a major obstacle in raising the bar of the overall user experience. Refreshing an
entire page is not very efficient. To address this issue, two key improvements were introduced:
Client-side scripting
Using Client-side Scripting
All browsers now provide the ability to run client-side scripts, which are predominantly written in JavaScript,
although others such as VBScript are also possible in some browsers. The ability to run scripts in the browser is a
huge improvement. For example, a script can hide or show a section or modify the format of the content based on
the user input. Since this happens on the client, no round-trip to the server is necessary. This makes the web site
seem much more responsive.
JavaScript can be disabled on the client and you should consider, and test, how your page will function
with scripting disabled.
Using AJAX
AJAX is an acronym for asynchronous JavaScript and XML. While a bit of a misnomer since it doesn't have to
be asynchronous, use JavaScript, or XML, the term refers to a collection of technologies that enable client-side
scripting to communicate with the web server outside of the typical page refresh scenario. In a nutshell, AJAX
uses JavaScript to request data from the web server. It then updates the page content using the Document Object
Model (DOM). This allows portions of the web page to be updated as needed without a complete refresh.
AJAX can also be used to call web services independently from the web server that is hosting the web page.
You can use this to access data provided by a third party such as stock quotes or currency conversion. You can
also call your own web services to perform real-time updates or load data based on user input. For example,
you can provide a product search feature and use AJAX to call a web service that returns the matching products.
Again, this is all independent of the standard page refresh paradigm.
Figure 1-2 illustrates the more robust model that most web sites use today.
Search WWH ::

Custom Search