<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>March Madness On Demand: Data Collection Service Architecture</title><link>http://blogs.msdn.com/rdoherty/archive/2009/04/15/march-madness-on-demand-data-collection-service-architecture.aspx</link><description>In my previous post I talked about how we used SQL Server 2008 Service Broker to improve the durability of a data collection service for our March Madness Video On-Demand Silverlight player. This post provides a bit of background on the architecture of</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>March Madness On Demand: Data Collection Service Architecture | Microsoft Share Point</title><link>http://blogs.msdn.com/rdoherty/archive/2009/04/15/march-madness-on-demand-data-collection-service-architecture.aspx#9551182</link><pubDate>Wed, 15 Apr 2009 22:02:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9551182</guid><dc:creator>March Madness On Demand: Data Collection Service Architecture | Microsoft Share Point</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://microsoft-sharepoint.simplynetdev.com/march-madness-on-demand-data-collection-service-architecture-2/"&gt;http://microsoft-sharepoint.simplynetdev.com/march-madness-on-demand-data-collection-service-architecture-2/&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>