<?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: Skype&#39;s Push for Cash</title>
	<atom:link href="http://www.markevanstech.com/2005/03/18/skypes-push-for-cash/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markevanstech.com/2005/03/18/skypes-push-for-cash/</link>
	<description>Insight and Analysis from North of the Border</description>
	<pubDate>Fri, 09 Jan 2009 00:56:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tim A</title>
		<link>http://www.markevanstech.com/2005/03/18/skypes-push-for-cash/comment-page-1/#comment-164</link>
		<dc:creator>Tim A</dc:creator>
		<pubDate>Fri, 18 Mar 2005 22:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://markevanstech.com/?p=407#comment-164</guid>
		<description>I don&#39;t think we&#39;ll be seeing any handsets or any other hardware connecting to Skype services. The absolute number one mistake I think Skype made early on was to develop their own protocol and disregard the VoIP protocols that were already in existence.
So, you won&#39;t be seeing any hardware makers adding yet another protocol to their devices when they work fine with the 99.999% of other VoIP providers services out there.</description>
		<content:encoded><![CDATA[<p>I don&#39;t think we&#39;ll be seeing any handsets or any other hardware connecting to Skype services. The absolute number one mistake I think Skype made early on was to develop their own protocol and disregard the VoIP protocols that were already in existence.<br />
So, you won&#39;t be seeing any hardware makers adding yet another protocol to their devices when they work fine with the 99.999% of other VoIP providers services out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
