<?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: Google’s OpenEdge Plan: Faster Internet Access for Google Content</title>
	<atom:link href="http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/</link>
	<description>Providing insight, analysis, and commentary on the evolving telecom competitive landscape</description>
	<lastBuildDate>Tue, 16 Mar 2010 22:59:55 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Zashkaser</title>
		<link>http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/comment-page-1/#comment-8002</link>
		<dc:creator>Zashkaser</dc:creator>
		<pubDate>Wed, 05 Aug 2009 16:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/#comment-8002</guid>
		<description>Very Interesting post! Thank you for such interesting resource!PS: Sorry for my bad english, I’v just started to learn this language</description>
		<content:encoded><![CDATA[<p>Very Interesting post! Thank you for such interesting resource!PS: Sorry for my bad english, I’v just started to learn this language</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/comment-page-1/#comment-4117</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 17 Dec 2008 04:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/#comment-4117</guid>
		<description>Service providers have been trying to find ways to deliver extra value to their subscribers over their broadband &quot;pipe&quot;.  Relationships such as Google&#039;s OpenEdge permit the service provider to deliver something special to their customer, and possibly, gain a portion of the ad revenue stream.

On the other hand, I can see how peering relationships between content and service providers could raise the hair of Net Neutrality folks.</description>
		<content:encoded><![CDATA[<p>Service providers have been trying to find ways to deliver extra value to their subscribers over their broadband &#8220;pipe&#8221;.  Relationships such as Google&#8217;s OpenEdge permit the service provider to deliver something special to their customer, and possibly, gain a portion of the ad revenue stream.</p>
<p>On the other hand, I can see how peering relationships between content and service providers could raise the hair of Net Neutrality folks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike T.</title>
		<link>http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/comment-page-1/#comment-4102</link>
		<dc:creator>Mike T.</dc:creator>
		<pubDate>Tue, 16 Dec 2008 13:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.telecompetitor.com/google%e2%80%99s-openedge-plan-faster-internet-access-for-google-content/#comment-4102</guid>
		<description>all google is doing is putting caching servers closer to the user. whats the fuss with that. thats been going on for years. i remember when all the internet &quot;experts&quot; were encouraging caching.</description>
		<content:encoded><![CDATA[<p>all google is doing is putting caching servers closer to the user. whats the fuss with that. thats been going on for years. i remember when all the internet &#8220;experts&#8221; were encouraging caching.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
