Individual AppPools vs. Shared Pooling
October 2, 2007
Many hosting companies have based their windows-based hosting environments on the concept of shared application pooling, by sharing AppPools those companies achieved server densities similar to those seen on Apache (Linux/Unix). But for any customer with a website that processes credit card information directly, or has proprietary scripts, this is really a significant problem. their sites share a security identity with the other sites in the same AppPool. A developer – using a coding technique called “RevertToSelf” – can view the code (in read-only mode) of all of the sites within the same AppPool.The problem this causes for the customer is that their site is not secure. the more things that can go wrong or cause the sites within that AppPool to crash – like the famous pooling crash between ASP.NET 1.1 and 2.0 – the more customers who will be affected by such a calamity.
Read more:
configuring Application Pools in IIS 6.0
running multiple ASP.NET applications
