In situations where server-side state is feasible and the limitations, such as requiring browser
cookies, are acceptable, server-side state can be a convenient method to store state for custom
controls. However, in this book, we do not use server-side state management techniques in any
of the samples, because doing so would require developer users of the server controls to enable
server-side state in order for the controls to work. Forcing server-side state on users is not a
good practice and would limit the desirability of the server controls.
ASP.NET and Client-Side State Management
ASP.NET provides access to a variety of client-side state management techniques to give you a
helping hand in building useful, interactive web sites. Control developers can leverage these
state management features to provide extra value in their controls by making it look as if the
controls can remember their previous values or obviate the need to go back to a data source to
display information for tabular controls. What makes this capability wonderful is that these
options do not require any special-purpose mechanism on the web server; instead, they use
the everyday features of a web browser to make this magic happen. In this section, we provide
an overview of the client-side state options that are available:
??? URL strings
??? Cookies
??? Hidden HTML variables
??? View state
Session State collection maintained on behalf of a web application user
Trace Debugging utility for writing to the trace output of the web form
User Makes security information available when a user is authenticated
Table 3-2.
Pages:
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166