<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Handling messages out of order</title>
	<atom:link href="http://www.udidahan.com/2007/12/15/handling-messages-out-of-order/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2007/12/15/handling-messages-out-of-order/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Thu, 11 Mar 2010 11:59:32 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: RG</title>
		<link>http://www.udidahan.com/2007/12/15/handling-messages-out-of-order/comment-page-1/#comment-13802</link>
		<dc:creator>RG</dc:creator>
		<pubDate>Wed, 09 Jan 2008 20:41:14 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/12/15/handling-messages-out-of-order/#comment-13802</guid>
		<description>Wow, the solution you propose is really ugly, the same as the previous solution with &#039;HandleCurrentMessageLater&#039;. Ugly because it&#039;s unsafe (has a race condition), non-transactional (a big mistake), error prone and impossible to debug. And what if you have 3 messages - A, B and C, that need to be handled in order - how would your logic look then? 
If you need to process messages in order, use a single thread and don&#039;t worry about performance. Or implement more intelligent algorithm that will handle messages in parallel only when they are &#039;unrelated&#039; - this is not very hard to do for a good programmer.</description>
		<content:encoded><![CDATA[<p>Wow, the solution you propose is really ugly, the same as the previous solution with &#8216;HandleCurrentMessageLater&#8217;. Ugly because it&#8217;s unsafe (has a race condition), non-transactional (a big mistake), error prone and impossible to debug. And what if you have 3 messages &#8211; A, B and C, that need to be handled in order &#8211; how would your logic look then?<br />
If you need to process messages in order, use a single thread and don&#8217;t worry about performance. Or implement more intelligent algorithm that will handle messages in parallel only when they are &#8216;unrelated&#8217; &#8211; this is not very hard to do for a good programmer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: udidahan</title>
		<link>http://www.udidahan.com/2007/12/15/handling-messages-out-of-order/comment-page-1/#comment-12808</link>
		<dc:creator>udidahan</dc:creator>
		<pubDate>Fri, 21 Dec 2007 07:31:05 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/12/15/handling-messages-out-of-order/#comment-12808</guid>
		<description>That&#039;ll be the next post - how to do it with workflow and what problems it solves. For this post, I assumed Bill&#039;s scenario was that he got the messages into the queue in the right order but the processing ended up being out of order.

But great question.</description>
		<content:encoded><![CDATA[<p>That&#8217;ll be the next post &#8211; how to do it with workflow and what problems it solves. For this post, I assumed Bill&#8217;s scenario was that he got the messages into the queue in the right order but the processing ended up being out of order.</p>
<p>But great question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayende Rahien</title>
		<link>http://www.udidahan.com/2007/12/15/handling-messages-out-of-order/comment-page-1/#comment-12549</link>
		<dc:creator>Ayende Rahien</dc:creator>
		<pubDate>Sun, 16 Dec 2007 08:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/12/15/handling-messages-out-of-order/#comment-12549</guid>
		<description>But doesn&#039;t this mean that a few milliseconds delay will cause a message to be bounced?
Isn&#039;t it more appropriate to handle this with a retry count?</description>
		<content:encoded><![CDATA[<p>But doesn&#8217;t this mean that a few milliseconds delay will cause a message to be bounced?<br />
Isn&#8217;t it more appropriate to handle this with a retry count?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
