ArticleDirectory
- IIS 5
- IIS 6 Classic Mode
- IIS 7 integration mode vs. Classic Mode
- Foreground thread vs background thread
- Worker thread vs. Io thread
- Permission
IIS 5
IIS (inetinfo.exe)-> ASP. net isapi (aspnet_isapi.dll)-> ASP. NET Worker Process (aspnet_wp.exe)->...
IIS 6 Classic Mode
IIS (inetinfo.exe)-> Asp. net Worker Process (w3wp.exe, application pool)-> Asp. net ISAPI (aspnet_isapi.dll)-> appdomain-> httpruntime. process (New httpworkerrequest ()-> httpapplicationfactory. getapplicationinstance ()-> httpapplication. beginprocessrequest (New
Httpcontext (workerrequest)-> ihttpmodule-> ihttphandlerfactory-> ihttphandler
IIS 7 integration mode vs. Classic Mode
IIS is a pipeline and a filter, and ASP. NET is also a pipeline and a filter. Simply don't wrap it around. It's just the integration mode.
Foreground thread vs background thread
Thread. isbackground = true, ApplicationProgramTo exit, you must wait for all foreground threads to exit, and do not have to wait for background threads.
Worker thread vs. Io thread
Threadpool itself is for performance, and the distinction between the two threads is also for performance. threadpool provides different treatment for the two threads.
Permission
<System. Web>
<Processmodel username = "" Password = ""/>
<Identity impersonate = "true" username = "" Password = ""/>
</System. Web>