<?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/"
	xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Rackspace breaks IPO drought</title>
	<atom:link href="http://brainstormtech.blogs.fortune.cnn.com/2008/08/06/racking-up-the-rackspace-ipo/feed/" rel="self" type="application/rss+xml" />
	<link>http://brainstormtech.blogs.fortune.cnn.com/2008/08/06/racking-up-the-rackspace-ipo/</link>
	<description>Fortune&#039;s tech team offers analysis and perspective on the world’s most important developments.</description>
	<lastBuildDate>Sun, 08 Nov 2009 00:10:22 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rich, Scotch Plains, NJ</title>
		<link>http://brainstormtech.blogs.fortune.cnn.com/2008/08/06/racking-up-the-rackspace-ipo/#comment-5268</link>
		<dc:creator>Rich, Scotch Plains, NJ</dc:creator>
		<pubDate>Mon, 11 Aug 2008 02:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://bigtech.wordpress.com/?p=1300#comment-5268</guid>
		<description>Sorry, Jon, you&#039;re still missing miliki&#039;s point.  The problems that Apple experience are software related, i.e. the services themselves caused the problem not the infrastructure.  Losing emails is a software problem, not a network or hardware problem.  But, Rackspace only does network and hardware.  The comparison, then, is not fair to Rackspace because they simply won&#039;t be facing the same obstacles.  Their client&#039;s might, but not Rackspace themselves.



&lt;strong&gt;From Jon Fortt:&lt;/strong&gt; First, there&#039;s plenty of software involved in what Rackspace does. Second, losing e-mail can also be a hardware problem, and Apple never explained what happened.</description>
		<content:encoded><![CDATA[<p>Sorry, Jon, you&#039;re still missing miliki&#039;s point.  The problems that Apple experience are software related, i.e. the services themselves caused the problem not the infrastructure.  Losing emails is a software problem, not a network or hardware problem.  But, Rackspace only does network and hardware.  The comparison, then, is not fair to Rackspace because they simply won&#039;t be facing the same obstacles.  Their client&#039;s might, but not Rackspace themselves.</p>
<p><strong>From Jon Fortt:</strong> First, there&#039;s plenty of software involved in what Rackspace does. Second, losing e-mail can also be a hardware problem, and Apple never explained what happened.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: miliki,chicago,IL</title>
		<link>http://brainstormtech.blogs.fortune.cnn.com/2008/08/06/racking-up-the-rackspace-ipo/#comment-5267</link>
		<dc:creator>miliki,chicago,IL</dc:creator>
		<pubDate>Wed, 06 Aug 2008 19:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://bigtech.wordpress.com/?p=1300#comment-5267</guid>
		<description>From Someone who works in the hosting business I can say that the comparison between rackspace and apple is incorrect. Apple&#039;s product was a Web Service, not hosting. Host only provide the computers for other to host their applications. The Web Service is the application and it was this that was Apple&#039;s problem.



&lt;strong&gt;From Jon Fortt:&lt;/strong&gt; But Apple also has a history of hosting its web services on its own infrastructure. So it ends up being a compound problem.</description>
		<content:encoded><![CDATA[<p>From Someone who works in the hosting business I can say that the comparison between rackspace and apple is incorrect. Apple&#039;s product was a Web Service, not hosting. Host only provide the computers for other to host their applications. The Web Service is the application and it was this that was Apple&#039;s problem.</p>
<p><strong>From Jon Fortt:</strong> But Apple also has a history of hosting its web services on its own infrastructure. So it ends up being a compound problem.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
