<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/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/"><channel><title>Reliable Azure Processes - Part 3 - Dealing with errors</title><link>http://blogs.msdn.com/neilkidd/archive/2008/12/10/reliable-azure-processes-part-3-dealing-with-errors.aspx</link><description>After the last 2 blog entries, we have our worker process's main loop feed back into Azure's heath checking system. If we go unhealthy, Azure will notice and will eventually restart the worker role. However, this is a bit heavy handed; what if the failure</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Reliable Azure Processes - Part 4 - Scaling Down!</title><link>http://blogs.msdn.com/neilkidd/archive/2008/12/10/reliable-azure-processes-part-3-dealing-with-errors.aspx#9221401</link><pubDate>Mon, 15 Dec 2008 19:55:52 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9221401</guid><dc:creator>Neil Kidd's Blog</dc:creator><description>&lt;p&gt;One thing that you need to consider when designing your Azure application is &amp;amp;quot; what is the minimum&lt;/p&gt;
</description></item><item><title>Building Reliable Azure Processes</title><link>http://blogs.msdn.com/neilkidd/archive/2008/12/10/reliable-azure-processes-part-3-dealing-with-errors.aspx#9407079</link><pubDate>Sun, 08 Feb 2009 18:33:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9407079</guid><dc:creator>&lt;/blog&gt;</dc:creator><description>&lt;p&gt;Neil Kidd has put together a great set of posts together to explain in detail how to create reliable&lt;/p&gt;
</description></item></channel></rss>