<?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>More Poison Message Handling</title><link>http://blogs.msdn.com/drnick/archive/2007/02/13/more-poison-message-handling.aspx</link><description>We saw the poison message handling strategies for MSMQ 3 and MSMQ 4 yesterday, but how many different strategies can we come up with? Let us count the ways. I've roughly ordered these by increasing complexity. Discard. We could simply throw away any message</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>MSMQ and Poison Messages</title><link>http://blogs.msdn.com/drnick/archive/2007/02/13/more-poison-message-handling.aspx#1670486</link><pubDate>Tue, 13 Feb 2007 21:36:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1670486</guid><dc:creator>Nicholas Allen's Indigo Blog</dc:creator><description>&lt;p&gt;Last time we looked at the idea of poison messages in queues - messages that are permanently unprocessable.&lt;/p&gt;
</description></item><item><title>New and Notable 142</title><link>http://blogs.msdn.com/drnick/archive/2007/02/13/more-poison-message-handling.aspx#1705828</link><pubDate>Sun, 18 Feb 2007 19:17:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1705828</guid><dc:creator>Sam Gentile</dc:creator><description>&lt;p&gt;Data/ADO.NET Orcas Two from the ADO.NET team: Entity Client and Nulls - LINQ to DataSets Part 3 Software&lt;/p&gt;
</description></item></channel></rss>