<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.iis.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:cs="http://blogs.iis.net/"><channel><title>IIS 7.0 Application Pools</title><link>http://blogs.iis.net/tomwoolums/archive/2008/12/17/iis-7-0-application-pools.aspx</link><description>Application pools, URLs or groups of URLs served by one set of worker processes, have many benefits. They set boundaries that contain applications an prevent them from affecting applications outside of the pool. So if one application fails it won't affect</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>re: IIS 7.0 Application Pools</title><link>http://blogs.iis.net/tomwoolums/archive/2008/12/17/iis-7-0-application-pools.aspx#2828574</link><pubDate>Wed, 24 Dec 2008 06:59:11 GMT</pubDate><guid isPermaLink="false">50bcf3b4-f6fe-4638-adff-0c150e922e99:2828574</guid><dc:creator>Anonymous</dc:creator><description>&lt;p&gt;Ya.. It's right&lt;/p&gt;
&lt;img src="http://blogs.iis.net/aggbug.aspx?PostID=2828574" width="1" height="1"&gt;</description></item></channel></rss>