IIS is a web server software developed by Microsoft. IIS provides a request processing architecture. IIS includes,
- A customizable web server engine by adding or removing modules
- Windows Process Activation Service (WAS) which enables sites to use protocols other than HTTP and HTTPS
- Integrated request processing pipelines from IIS and ASP.NET
Components in IIS
Performs important functions in IIS. Some components of IIS are protocol listeners (HTTP.sys) and services such as World Wide Web publishing service (WWW Service) Windows Process Activation Service (WAS).
Protocol listeners
These receive protocol specific requests, send them to IIS for processing and returns responses. One example is HTTP.sys HTTP listener which listens to both HTTP and HTTPS. You can also use protocol listeners for WCF etc.
Following video will show you how to host WCF services in IIS.
Managed code modules that implements IHttpModule has access to all events in request pipeline. In IIS6 and IIS7 classic mode, ASP.NET request pipeline was separate from Web server pipeline. But in IIS 7, it is a unified pipeline which handles the requests.
In ASP.NET application life cycle, firstly
Automatic Deployment using Microsoft Web Deploy
http://weblogs.asp.net/scottgu/automating-deployment-with-microsoft-web-deploy
These receive protocol specific requests, send them to IIS for processing and returns responses. One example is HTTP.sys HTTP listener which listens to both HTTP and HTTPS. You can also use protocol listeners for WCF etc.
Windows Process Activation Service (WAS)
By default IIS only supports HTTP protocol. You can use WAS component to enable other protocols. Also see http://www.iis.net/learn/manage/provisioning-and-managing-iis/features-of-the-windows-process-activation-service-wasFollowing video will show you how to host WCF services in IIS.
Pipelines
In IIS 7 there are 2 request processing pipelines. Classic and Integrated pipeline. Classic was the only existed in IIS 6 and below. With Integrated pipeline it is tightly integrated as ASP.NET request pipeline. (SO)Managed code modules that implements IHttpModule has access to all events in request pipeline. In IIS6 and IIS7 classic mode, ASP.NET request pipeline was separate from Web server pipeline. But in IIS 7, it is a unified pipeline which handles the requests.
In ASP.NET application life cycle, firstly
- The ApplicationManager and HostingEnvironment objects gets created
- Application objects such as HttpContext, HttpRequest gets created
- HttpApplication object is created (if one doesn't exist to use) and assigned to the request
Automatic Deployment using Microsoft Web Deploy
http://weblogs.asp.net/scottgu/automating-deployment-with-microsoft-web-deploy
Resources
http://www.c-sharpcorner.com/uploadfile/suresh_g_v2002/introduction-on-iis-7/
https://msdn.microsoft.com/en-us/library/bb470252(v=vs.140).aspx
https://msdn.microsoft.com/en-us/library/bb470252(v=vs.140).aspx
0 comments:
Post a Comment