<?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: Redundant Arrays of Internet Service Providers (RAISP) for 100% Uptime</title>
	<atom:link href="http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/</link>
	<description>Charles Merriam&#039;s loud tales of coding and technology</description>
	<lastBuildDate>Sun, 02 May 2010 17:08:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: spenser</title>
		<link>http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/comment-page-1/#comment-15178</link>
		<dc:creator>spenser</dc:creator>
		<pubDate>Tue, 20 May 2008 08:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.charlesmerriam.com/blog/?p=79#comment-15178</guid>
		<description>To deal with the hosting providers that disallow media-only web serving, you can do two things. First, completely mirror the site. Second, have the ip included as part of the set answering for that site.

Of course, if RAISP spreads, then hosting providers will have to reconsider their TOS.

As for the stupid dns tricks needed to accomplish this, you can get a third party service that supports *all* of the features you need from:

&lt;a href=&quot;http://edgedirector.com/&quot; rel=&quot;nofollow&quot;&gt;edgedirector.com&lt;/a&gt;

It&#039;s the little things that will make or break the concept. Things like: failback control strategy, second tier failover, geoip, load shedding and monitoring. This requires a great deal of research and coding that needs to have its cost spread over multiple customers. Thus, a third party managed dns service.</description>
		<content:encoded><![CDATA[<p>To deal with the hosting providers that disallow media-only web serving, you can do two things. First, completely mirror the site. Second, have the ip included as part of the set answering for that site.</p>
<p>Of course, if RAISP spreads, then hosting providers will have to reconsider their TOS.</p>
<p>As for the stupid dns tricks needed to accomplish this, you can get a third party service that supports *all* of the features you need from:</p>
<p><a href="http://edgedirector.com/" rel="nofollow">edgedirector.com</a></p>
<p>It&#8217;s the little things that will make or break the concept. Things like: failback control strategy, second tier failover, geoip, load shedding and monitoring. This requires a great deal of research and coding that needs to have its cost spread over multiple customers. Thus, a third party managed dns service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kee Hinckley</title>
		<link>http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/comment-page-1/#comment-6593</link>
		<dc:creator>Kee Hinckley</dc:creator>
		<pubDate>Sat, 10 Nov 2007 07:04:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.charlesmerriam.com/blog/?p=79#comment-6593</guid>
		<description>Two quick thoughts.

1. I know that at least one of my hosting providers specifically disallows media-only web serving.

2. As for technological solutions, it might actually make sense to look at how spammers do this (with owned machines) since the techniques they use might well work for legitimate servers as well.</description>
		<content:encoded><![CDATA[<p>Two quick thoughts.</p>
<p>1. I know that at least one of my hosting providers specifically disallows media-only web serving.</p>
<p>2. As for technological solutions, it might actually make sense to look at how spammers do this (with owned machines) since the techniques they use might well work for legitimate servers as well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: charles</title>
		<link>http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/comment-page-1/#comment-6559</link>
		<dc:creator>charles</dc:creator>
		<pubDate>Fri, 09 Nov 2007 07:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.charlesmerriam.com/blog/?p=79#comment-6559</guid>
		<description>Which part?  The DNS for failover or playing with BGP messages to keep the DNS resolution bouncing?</description>
		<content:encoded><![CDATA[<p>Which part?  The DNS for failover or playing with BGP messages to keep the DNS resolution bouncing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Weber</title>
		<link>http://www.charlesmerriam.com/blog/2007/11/redundant-arrays-of-internet-service-providers-raisp-for-100-uptime/comment-page-1/#comment-6553</link>
		<dc:creator>Chris Weber</dc:creator>
		<pubDate>Fri, 09 Nov 2007 03:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.charlesmerriam.com/blog/?p=79#comment-6553</guid>
		<description>Could you elaborate on tactic 1?

Specifically, how would you accomplish this?</description>
		<content:encoded><![CDATA[<p>Could you elaborate on tactic 1?</p>
<p>Specifically, how would you accomplish this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

