<?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: Relying on Applications in the &#8216;Cloud&#8217;</title>
	<atom:link href="http://iconnectdots.com/2008/07/when-can-we-rel.html/feed" rel="self" type="application/rss+xml" />
	<link>http://iconnectdots.com/2008/07/when-can-we-rel.html</link>
	<description>Guidance, Insight and Ideas in a Time of Accelerating Change</description>
	<lastBuildDate>Fri, 10 Feb 2012 00:45:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jeff</title>
		<link>http://iconnectdots.com/2008/07/when-can-we-rel.html/comment-page-1#comment-128</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Wed, 30 Jul 2008 05:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://iconnectdots.com.s11974.gridserver.com/2008/07/relying-on-applications-in-the-cloud.html#comment-128</guid>
		<description>Let&#039;s face it, Twitter is in the midst of completely overhauling their infrastructure - on the fly. I for one am willing to continue to cut them some slack for the next couple months.

Secondly, I agree that corporations need to begin studying the various microblog channels. Monitoring your brand should be the first step. Determining why, how and when should engage the channel is the next step. Take your time - 98% of America still doesn&#039;t even know what Twitter is yet - you&#039;ve got time to architect a strategy that makes sense for your organization.

In terms of living &quot;in the cloud&quot;, services will continue to improve their reliability, and I&#039;m confident that over time cloud computing will deliver greater uptime than current configurations.

Having said that, I completely agree that one must fully understand the potential ramifications of mapping mission-critical processes to 3rd party apps, no matter what their delivery vehicle.

In other words.... Living in the cloud is a good thing, just be careful who you hang out with
</description>
		<content:encoded><![CDATA[<p>Let&#8217;s face it, Twitter is in the midst of completely overhauling their infrastructure &#8211; on the fly. I for one am willing to continue to cut them some slack for the next couple months.</p>
<p>Secondly, I agree that corporations need to begin studying the various microblog channels. Monitoring your brand should be the first step. Determining why, how and when should engage the channel is the next step. Take your time &#8211; 98% of America still doesn&#8217;t even know what Twitter is yet &#8211; you&#8217;ve got time to architect a strategy that makes sense for your organization.</p>
<p>In terms of living &#8220;in the cloud&#8221;, services will continue to improve their reliability, and I&#8217;m confident that over time cloud computing will deliver greater uptime than current configurations.</p>
<p>Having said that, I completely agree that one must fully understand the potential ramifications of mapping mission-critical processes to 3rd party apps, no matter what their delivery vehicle.</p>
<p>In other words&#8230;. Living in the cloud is a good thing, just be careful who you hang out with</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bex</title>
		<link>http://iconnectdots.com/2008/07/when-can-we-rel.html/comment-page-1#comment-127</link>
		<dc:creator>bex</dc:creator>
		<pubDate>Tue, 29 Jul 2008 23:35:30 +0000</pubDate>
		<guid isPermaLink="false">http://iconnectdots.com.s11974.gridserver.com/2008/07/relying-on-applications-in-the-cloud.html#comment-127</guid>
		<description>What you need is a &quot;cloud backup,&quot; something that acts as a functionality cache while the cloud is down.

They need Twitter &quot;appliances&quot; that sync-back with the original Twitter server. Something that allows you to manage some stuff locally, but eventually spread it to all nodes.

huh... sounds a bit like Usenet, doesn&#039;t it?
</description>
		<content:encoded><![CDATA[<p>What you need is a &#8220;cloud backup,&#8221; something that acts as a functionality cache while the cloud is down.</p>
<p>They need Twitter &#8220;appliances&#8221; that sync-back with the original Twitter server. Something that allows you to manage some stuff locally, but eventually spread it to all nodes.</p>
<p>huh&#8230; sounds a bit like Usenet, doesn&#8217;t it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

