<?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: NServiceBus easily extensible</title>
	<atom:link href="http://www.udidahan.com/2007/07/30/nservicebus-easily-extensible/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2007/07/30/nservicebus-easily-extensible/</link>
	<description>Enterprise Development Expert &#38; SOA Specialist</description>
	<lastBuildDate>Fri, 23 Jul 2010 18:21:18 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Andreas</title>
		<link>http://www.udidahan.com/2007/07/30/nservicebus-easily-extensible/comment-page-1/#comment-3840</link>
		<dc:creator>Andreas</dc:creator>
		<pubDate>Sun, 05 Aug 2007 17:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2007/07/30/nservicebus-easily-extensible/#comment-3840</guid>
		<description>I have made a version of my filetransport that uses the transactional file system in vista. But my original filetransport design writes the messages directly to the destination directory. The TxF doesn&#039;t work when you manipulate files on network shares. So currently it only work with the client and server on the same machine. This is obviously not good enough so I will change the design to work transactionally with a local directory and then have the worker threads move those files across the network. I guess that I will end up writing a &quot;light weight MSMQ&quot; :) Do you have any suggestions for alternate designs using the TxF?</description>
		<content:encoded><![CDATA[<p>I have made a version of my filetransport that uses the transactional file system in vista. But my original filetransport design writes the messages directly to the destination directory. The TxF doesn&#8217;t work when you manipulate files on network shares. So currently it only work with the client and server on the same machine. This is obviously not good enough so I will change the design to work transactionally with a local directory and then have the worker threads move those files across the network. I guess that I will end up writing a &#8220;light weight MSMQ&#8221; <img src='http://www.udidahan.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Do you have any suggestions for alternate designs using the TxF?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
