Monday, June 2, 2008

ASP.NET Internals Request Architecture(Lesson3)

How the worker process loads the web application.

Read first
ASP.NET Internals Request Architecture(Lesson1)
ASP.NET Internals Request Architecture(Lesson2)

Let’s examine some details about how the worker process loads the web application.
1-The worker process loads the web application assembly.
2- Allocating one application domain for the application.

When the worker process 3-starts a web application (in its application domain),
4-The web application inherits the identity of the process (NetworkService by default)

LoadApp
if impersonation is disabled. However, if impersonation is enabled, each web application runs under the account that is authenticated by IIS or the user account that is configured in the web.config.

  • Identity impersonate=”true”
    • If only anonymous access is enabled by IIS, the identity that is passed to the web application will be [machine]\IUSR_[machine]
    • If only integrated Windows authentication is enabled in IIS, the identity that is passed to the web application will be the authenticated windows user.
    • If both integrated windows authentication and anonymous access are enabled, the identity that is passed to the web application will depend on the one that was authenticated by IIS. IIS first attempts to use anonymous access to grant a user access to a web application resource. If this attempt fails, it then tries to use windows authentication
  • Identity impersonate=”true” username=”username” password=”password” This allows the web application to run under specific identity

IIS Ipersonate

Thx Hope lesson 3 be useful for U ... tomorrow will Complete with
Differences between IIS 6.0 , IIS 5.0 and IIS 7.0 in the way they handle requests.

References
http://www.codeproject.com/KB/aspnet/aspnetrequestarchitecture.aspx
http://www.codeproject.com/KB/aspnet/aspnetviewstatepagecycle.aspx
http://www.codeproject.com/KB/aspnet/PageLifeCycle.aspx

Why Develop for Windows Vista

As a developer, you can differentiate your applications with Windows Vista through innovative user experience, providing new ways to help users be productive and making applications more relevant—and just plain fun to use. New features make it easy to develop applications that communicate across the enterprise, around the world, as well as with nearby devices and machines. Windows Vista also provides a new set of APIs that help you make applications more predictable, manageable, and secure.

Security, Reliability and Manageability, and Error Reporting.

1. Run Securely

Visit Security in Windows Vista for comprehensive information.

2. Design for Reliability and Management


3. Establish a Customer Feedback Loop


User Experience

1. Follow the Windows Vista User Experience Guidelines


2. Enrich the User Experience


3. Enable Users to Visualize, Organize, and Search

Get Connected

1. Get Connected with Core Technologies


2. Bring Data to Users with RSS


3. Make Document Data Accessible


4. Build for Mobility