ASP. NET Framework (1)

ASP. NET Framework (1) March 25, 2004

I remember that some time ago I had a good book called Delphi for an in-depth adventure. I also borrowed it for the moment ,:) Here I do not want to briefly introduce ASP. net, Asp. in addition to the old ASP. net, you are familiar with sessions, applications, and so on, but do not try to draw equal signs for sessions in the ancient ASP era. Let's go deep into the core of ASP. NET Framework to see how she implemented it and how she assumed the reputation of the next-generation Web development technology platform. This article has never thought about how many chapters to complete, nor does it need to. The form of privilege as a diary may be very short or very long. I will do my best to put ASP.. NET Framework. If you have no knowledge of ASP. NET Framework, you can become a master of ASP. NET coding. Chapter One -- process a HTTP request. Let's take a look at the operating mechanism and architecture of ASP. NET Framework. Before we start, we will first follow the archaeologists to visit the ancient ASP operating mechanism: When you request *. when the ASP file is used, the HTTP requestfirst is intercepted by the inetinfo.exeprocess. The inetinfo.exe process is the WWW Service process, and then she will forward the request to ASP. DLL process, Asp. the DLL process will explain and execute this ASP leaf, and then return the interpreted data stream to the client browser. Let's look at how ASP. NET Framework processes an HTTP request. When you request *. when the aspx file is used, the same HTTP requestwill be intercepted by the inetinfo.exe process. After judging the file suffix, she transfers the request to aspnet_isapi.dll. aspnet_isapi.dll is called an HTTP response process, after the HTTP requestenters the aspnet_wp.exe process, the request is processed through httpruntime and the result is returned to the client. OK, it seems that there is not much improvement. Don't worry. in ASP. NET Framework, we can even learn the httpruntime details. Okay. Continue on: After the HTTP request enters httpruntime, it will continue to enter a iner called httpapplication factory. She will give an httpapplication to process the passed request, this request will go to the following container: httpmodule-> httphandler factory-> httphandler. After the processresquest method of httphandler in the system is processed, the entire HTTP request is complete, and the client gets the corresponding stuff. Sort out the process of processing an HTTP request using ASP. NET Framework: Httprequest --> inetinfo.exe --> response --> HTTP pipeline --> aspnet_wp.exe --> httpruntime --> httpapplication factory --> httpapplication --> httpmodule --> httphandler factory --> httphandler. processrequest () I may ask, do I know the usefulness of this processing process? Of course, this is useful. For example, if you want to intercept an HTTP request and perform some processing on your own, what should you do? This is what we will discuss next time. Next time we will discuss in detail the details of the issue. See you later