<?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: Thinking Out Cloud &#8211; The Market Data Sweet Spot</title>
	<atom:link href="http://xignite.web-services-blog.com/2010/02/thinking-out-cloud-the-market-data-sweet-spot/feed/" rel="self" type="application/rss+xml" />
	<link>http://xignite.web-services-blog.com/2010/02/thinking-out-cloud-the-market-data-sweet-spot/</link>
	<description>It&#039;s not the data.  It&#039;s the delivery.</description>
	<lastBuildDate>Thu, 19 Jan 2012 20:29:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Thinking Out Cloud – Mass Customization and Market Data &#124; Financial Market Data Web Services - Xignite Blog</title>
		<link>http://xignite.web-services-blog.com/2010/02/thinking-out-cloud-the-market-data-sweet-spot/comment-page-1/#comment-3483</link>
		<dc:creator>Thinking Out Cloud – Mass Customization and Market Data &#124; Financial Market Data Web Services - Xignite Blog</dc:creator>
		<pubDate>Tue, 13 Apr 2010 16:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://xignite.web-services-blog.com/?p=966#comment-3483</guid>
		<description>[...] rather, have it your way at a cost you can afford. In the last installment in this series entitled Thinking Out Cloud – The Market Data Sweet Spot, I pointed out that the best way to identify market data that can benefit from cloud computing is [...]</description>
		<content:encoded><![CDATA[<p>[...] rather, have it your way at a cost you can afford. In the last installment in this series entitled Thinking Out Cloud – The Market Data Sweet Spot, I pointed out that the best way to identify market data that can benefit from cloud computing is [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

