<?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: SaaS Headaches</title>
	<atom:link href="http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/</link>
	<description>Real Web Admins.  Real World Experience.</description>
	<lastBuildDate>Mon, 06 Feb 2012 14:28:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: SaaS</title>
		<link>http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/comment-page-1/#comment-735</link>
		<dc:creator>SaaS</dc:creator>
		<pubDate>Thu, 02 Jun 2011 05:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://webadminblog.com/?p=29#comment-735</guid>
		<description>Thankfully as time has gone by the offerings from SaaS have matured and many, if not all, of these concerns have been addressed and overcome.  Thanks for the post.</description>
		<content:encoded><![CDATA[<p>Thankfully as time has gone by the offerings from SaaS have matured and many, if not all, of these concerns have been addressed and overcome.  Thanks for the post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beware the Deceptive SLA, My Friend &#171; the agile admin</title>
		<link>http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/comment-page-1/#comment-627</link>
		<dc:creator>Beware the Deceptive SLA, My Friend &#171; the agile admin</dc:creator>
		<pubDate>Fri, 04 Jun 2010 22:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://webadminblog.com/?p=29#comment-627</guid>
		<description>[...] availability service level agreements (SLAs).  I discussed this topic some in my previous &#8220;SaaS Headaches&#8221; post.  I thought it would be instructive to show people the standard kind of &#8220;defense [...]</description>
		<content:encoded><![CDATA[<p>[...] availability service level agreements (SLAs).  I discussed this topic some in my previous &#8220;SaaS Headaches&#8221; post.  I thought it would be instructive to show people the standard kind of &#8220;defense [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beware the Deceptive SLA, My Friend - Web Admin Blog</title>
		<link>http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/comment-page-1/#comment-128</link>
		<dc:creator>Beware the Deceptive SLA, My Friend - Web Admin Blog</dc:creator>
		<pubDate>Fri, 12 Sep 2008 15:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://webadminblog.com/?p=29#comment-128</guid>
		<description>[...] availability service level agreements (SLAs).  I discussed this topic some in my previous &#8220;SaaS Headaches&#8221; post.  I thought it would be instructive to show people the standard kind of &#8220;defense [...]</description>
		<content:encoded><![CDATA[<p>[...] availability service level agreements (SLAs).  I discussed this topic some in my previous &#8220;SaaS Headaches&#8221; post.  I thought it would be instructive to show people the standard kind of &#8220;defense [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.webadminblog.com/index.php/2008/07/15/saas-headaches/comment-page-1/#comment-69</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Tue, 22 Jul 2008 19:21:18 +0000</pubDate>
		<guid isPermaLink="false">http://webadminblog.com/?p=29#comment-69</guid>
		<description>Great blog post.  Any time you are dealing with any sort of 3rd party vendor (SaaS or otherwise), you should always make sure that their polcies are at least as restrictive as your own.</description>
		<content:encoded><![CDATA[<p>Great blog post.  Any time you are dealing with any sort of 3rd party vendor (SaaS or otherwise), you should always make sure that their polcies are at least as restrictive as your own.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

