About Me

A career professional with 19 years of experiences with in application development, solution architecture, management and strategy. Architected, planned, and executed, many programs, projects and solutions delivering valued results to business clients and customers. Able to provide creative solutions to solve problems and articulate the value proposition to upper management and technical design to IT staff. Collaborates across teams and other facet of IT (i.e. operations, infrastructure, security) to validate solutions for completeness. Interface with clients to gather feedback, advise, and solution in the business language.

Monday, August 9, 2010

Application Pools pertaining to SharePoint

Application Pool

Application pools are a security and process boundary for a set of IIS web applications. Multiple web application can run in a single worker process. Application pools should be create if processes need to be isolated for stability or security. Especially if the web application is going to be going to be used with custom code or has request and proceses intensive sites.

When should an application pool be created?
An application pool should be created if an application has custom code or has multiple memory and processes intensive sites. Also if the application is deemed missing critical and uptime is the utmost importance then this might warrant an app pool.

More background Information:

The Http.sys is responsible for getting http request and send responses back to users.

Http.sys -----> Listen --> Queues -->(Isolation mode send to worker process) --> Responses

Worker Process -> A processes that runs in user mode to process a request from the Http.sys queue. The worker process runs in it's own process space so it want interfere with other http processes that are on a different process. After the worker process processes the request it use Http.sys to send it response back.

No comments:

Post a Comment