<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Protocol Bridging with Routing Services</title><link>http://blogs.technet.com/b/meamcs/archive/2012/05/11/protocol-bridging-with-routing-services.aspx</link><description>Introduction 
 In this post, I will try to explain the motives behind using routing services as transport bridging with a sample solution. With references to WCF 4.0, other stuff, this will be interesting journey. 
 Before going into details, let&amp;rsquo;s</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Protocol Bridging with Routing Services</title><link>http://blogs.technet.com/b/meamcs/archive/2012/05/11/protocol-bridging-with-routing-services.aspx#3507637</link><pubDate>Thu, 05 Jul 2012 20:40:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3507637</guid><dc:creator>Mario Boisclair</dc:creator><description>&lt;p&gt;Thank you very much for this very clear primer. The pictures help a lot.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3507637" width="1" height="1"&gt;</description></item></channel></rss>