The asp era is over, and the web era is approaching. Asp. net2.0 is highly encapsulated by MS, and development under vs.net is completely silly, but I don't want to be a coding man.
In the past asp era, when a *. asp file is requested, the request is first intercepted by a task manager named inetinfo.exe, and inetinfo.exe is actually a www Service. After Inetinfo.exe is intercepted, it immediately gives control to an asp. dll process, asp. ddl will explain and execute this asp page, and then return the data stream to the client browser. If you are an XP system, you can find the file in the C: "WINDOWS" system32 "inetsrv directory, at this time, asp should be interpreted and executed through explanation. Every request should be explained from the beginning. This is the most painful thing in the world.
Since there are newer technologies, and of course new technologies are to be used, the old technologies do not mean you are dedicated.
In asp. in the net2.0 era, when a client requests a *. aspxfile from IIS, the request is also caught in the same way as that in inetinfo.exe. after inetinfo.exe judges the file suffix, it forwards the request to aspnet_isapi.dll (you can go to C: "WINDOWS. NET "Framework" worker process, (you can go to C: "WINDOWS" Microsoft. NET "Framework" v2.0.50727directory to find the file, at the same time in the task manager can also find the terminal, A New Year httprequest into the aspnet_wp.exe process, asp.net framework will process this request through httpRuntime, and then send the data stream back to the client browser.
Men who only like to chat with beautiful women are never good men. We can regard HttpRuntime as a pretty girl. Since she is a pretty girl, of course she has to study it. What is HttpRuntime? She is not an entity, but an abstract environment that executes asp.net. It is important to remember this. Let's take a look at how HttpRuntime is executed? After an http request enters httpRuntime, the request will be sent to a Factory named HttpApplication Factory. The Factory generates an HttpApplication instance for the http request, the instance is then sent to the HttpModule container, and then the http request continues to be sent to the HttpHandler Factory,
The factory will also generate an HttpHandler instance. The processRequire method of this instance processes the incoming requests, and then delivers the processed results and control to the HttpModule container, the HttpModule container then sends the data stream processed from the HttpHandler instance back to the browser at the clinet end, so that the perfect life cycle of an Http request is over.
Remember, the place where the Http request is actually processed is in the processRequire method of the HttpHandler instance, and the last place where the data stream is sent back to the client is in the HttpModule container.
- Encode and determine the data value in DataBound event processing
- Use ASP. NET 2.0 FormView to display data
- Format cells in ASP. NET DetailsView
- How to encode the data value in the DataBound event
- DetailsView display data by PAGE