Deciding how much functionality
to place client-side (in JavaScript) and server-side (e.g., in C#) is one of the key
design issues you have to address when implementing AJAX applications. We??™ll discuss
this more later.
Some of the server controls are straightforward and map closely to standard HTML
tags, effectively providing a server-side implementation of those tags. Others are largerscale
abstractions that encapsulate complex GUI tasks such as a calendar or grid. It??™s
important to note that the server controls are not ActiveX controls or Java applets; the
control??™s server-side code generates a combination of HTML (to display the control) and
JavaScript (to provide the client-side functionality of the code), which is rendered in the
client??™s browser.
Several types of server controls exist:
HTML server controls: These classes wrap standard HTML tags. Within the ASP.NET
web page (usually with the .aspx file extension), the HTML tags have a runat="server"
attribute added to them. An example is the HtmlAnchor control, which is a server-side
representation of the
, or anchor, tag.
Pages:
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63