<?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: Managing Long-Lived Transactions with MassTransit.Saga</title>
	<atom:link href="http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/</link>
	<description>Software Architecture, .NET, SOA</description>
	<lastBuildDate>Wed, 10 Mar 2010 11:21:59 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18544</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 03 Sep 2008 22:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18544</guid>
		<description>Good point. I&#039;m going to add a transaction usage around the saga so that it is properly constrained - but what about a new saga instance? That has yet to be inserted into the database. While the window of opportunity is small, it does seem like it could happen.

I could persist the saga once it is created. The table would have to allow null/empty in everything since it would be an early shot. Thoughts on this? I certainly appreciate your advice and am going to apply our patch once I have transactions in the repository.</description>
		<content:encoded><![CDATA[<p>Good point. I&#8217;m going to add a transaction usage around the saga so that it is properly constrained &#8211; but what about a new saga instance? That has yet to be inserted into the database. While the window of opportunity is small, it does seem like it could happen.</p>
<p>I could persist the saga once it is created. The table would have to allow null/empty in everything since it would be an early shot. Thoughts on this? I certainly appreciate your advice and am going to apply our patch once I have transactions in the repository.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayende Rahien</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18543</link>
		<dc:creator>Ayende Rahien</dc:creator>
		<pubDate>Wed, 03 Sep 2008 19:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18543</guid>
		<description>Chris,
That is because you are not using transactions for this.</description>
		<content:encoded><![CDATA[<p>Chris,<br />
That is because you are not using transactions for this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MassTransit 0.3 Released - PhatBoyG</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18542</link>
		<dc:creator>MassTransit 0.3 Released - PhatBoyG</dc:creator>
		<pubDate>Wed, 03 Sep 2008 15:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18542</guid>
		<description>[...] Saga Support Long-lived transactions (Saga) are now supported and can be built using MassTransit. You can read all about that on my previous blog entry. [...]</description>
		<content:encoded><![CDATA[<p>[...] Saga Support Long-lived transactions (Saga) are now supported and can be built using MassTransit. You can read all about that on my previous blog entry. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MassTransit 0.3 Released</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18541</link>
		<dc:creator>MassTransit 0.3 Released</dc:creator>
		<pubDate>Wed, 03 Sep 2008 15:21:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18541</guid>
		<description>[...]     Managing Long-Lived Transactions with MassTransit.Saga   Sep [...]</description>
		<content:encoded><![CDATA[<p>[...]     Managing Long-Lived Transactions with MassTransit.Saga   Sep [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18523</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 29 Aug 2008 14:36:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18523</guid>
		<description>The save was added so that the state of the saga could be persisted before the publish of the next message. In some of my tests, I would actually get the next message and start processing it before the saga had been persisted, making it fail since it could not find the saga instance in the repository.</description>
		<content:encoded><![CDATA[<p>The save was added so that the state of the saga could be persisted before the publish of the next message. In some of my tests, I would actually get the next message and start processing it before the saga had been persisted, making it fail since it could not find the saga instance in the repository.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ayende Rahien</title>
		<link>http://blog.phatboyg.com/2008/08/28/managing-long-lived-transactions-with-masstransitsaga/comment-page-1/#comment-18522</link>
		<dc:creator>Ayende Rahien</dc:creator>
		<pubDate>Fri, 29 Aug 2008 11:46:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.phatboyg.com/?p=675#comment-18522</guid>
		<description>It looks good.
I really like the way you do registration for that.
One question, why do I need to explicitly save the saga?</description>
		<content:encoded><![CDATA[<p>It looks good.<br />
I really like the way you do registration for that.<br />
One question, why do I need to explicitly save the saga?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
