After all registered HttpModule objects have a chance to process events, the request is
shepherded to the appropriate HTTP handler by calling its ProcessRequest() method. The
ProcessRequest() method takes one parameter of type HttpContext containing the user state of
the current request. Next, HttpHandler is responsible for generating a response to the request
using the Context.Response.Write() method. This entire process is illustrated in Figure 3-1.
As you can see, request processing flows through a series of ASP.NET objects that have full
access to the ASP.NET state. The ASP.NET classes in Figure 3-2 can examine the state of a user
request to implement authentication, authorization, and auditing in a web application. These
objects also implement numerous useful events that can be extended. The ASP.NET classes
that manage user state flow and request processing are shown in the figure. Note that the familiar
Request, Response, Application, and Session objects are implemented via classes in this section
of the ASP.NET class hierarchy as part of the HttpContext class.
The ASP.NET request processing architecture permits developers to plug into the architecture
by authoring custom objects that implement the HttpHandler or HttpModule class.
Pages:
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161