<?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 Version 1.7 Available</title>
	<atom:link href="http://www.udidahan.com/2008/02/11/nservicebus-version-17-available/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.udidahan.com/2008/02/11/nservicebus-version-17-available/</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: udidahan</title>
		<link>http://www.udidahan.com/2008/02/11/nservicebus-version-17-available/comment-page-1/#comment-16897</link>
		<dc:creator>udidahan</dc:creator>
		<pubDate>Tue, 12 Feb 2008 11:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2008/02/11/nservicebus-version-17-available/#comment-16897</guid>
		<description>Stijn,

It shouldn’t be much work given that Service Broker is built around the same model of one-way, store and forward messaging.

You would implement the ITransport interface below, and configure it instead of the MsmqTransport implementation.

Does that answer your question?

&lt;pre&gt;
using System;
using System.Collections.Generic;

namespace NServiceBus.Unicast.Transport
{
  public interface ITransport : IDisposable
  {
    void Start();
    IList MessageTypesToBeReceived { set; }

    int NumberOfWorkerThreads { get; }
    void ChangeNumberOfWorkerThreads(int targetNumberOfWorkerThreads);

    void Send(TransportMessage m, string destination);
    void ReceiveMessageLater(TransportMessage m);

    int GetNumberOfPendingMessages();

    string Address { get; }

    event EventHandler TransportMessageReceived;

   void AbortHandlingCurrentMessage();
  }
}
&lt;/pre&gt;</description>
		<content:encoded><![CDATA[<p>Stijn,</p>
<p>It shouldn’t be much work given that Service Broker is built around the same model of one-way, store and forward messaging.</p>
<p>You would implement the ITransport interface below, and configure it instead of the MsmqTransport implementation.</p>
<p>Does that answer your question?</p>
<pre>
using System;
using System.Collections.Generic;

namespace NServiceBus.Unicast.Transport
{
  public interface ITransport : IDisposable
  {
    void Start();
    IList MessageTypesToBeReceived { set; }

    int NumberOfWorkerThreads { get; }
    void ChangeNumberOfWorkerThreads(int targetNumberOfWorkerThreads);

    void Send(TransportMessage m, string destination);
    void ReceiveMessageLater(TransportMessage m);

    int GetNumberOfPendingMessages();

    string Address { get; }

    event EventHandler TransportMessageReceived;

   void AbortHandlingCurrentMessage();
  }
}
</pre>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stijn Dreezen</title>
		<link>http://www.udidahan.com/2008/02/11/nservicebus-version-17-available/comment-page-1/#comment-16880</link>
		<dc:creator>Stijn Dreezen</dc:creator>
		<pubDate>Tue, 12 Feb 2008 09:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://udidahan.weblogs.us/2008/02/11/nservicebus-version-17-available/#comment-16880</guid>
		<description>How much work would we have and where exactly would we need to hook in if we&#039;d take MSMQ out of the picture and use SQL Server as the persistent store for the queue?</description>
		<content:encoded><![CDATA[<p>How much work would we have and where exactly would we need to hook in if we&#8217;d take MSMQ out of the picture and use SQL Server as the persistent store for the queue?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
