<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Google Talk Ups the Ante</title>
	<link>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/</link>
	<description>This and that on this and that</description>
	<pubDate>Sat, 31 Jul 2010 21:35:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Google Talk Ups the Ante by: Charlie Paglee</title>
		<link>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-79</link>
		<pubDate>Wed, 04 Jan 2006 21:16:04 +0000</pubDate>
		<guid>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-79</guid>
					<description>&lt;blockquote&gt; I don’t see any major threat to any of the existing VoIP clients anytime soon. At least not until Google can figure out a way to provide other compatible VoIP clients connectivity to PSTN networks at a price-point comparable to Skype, Yahoo, and the rest of the gang.&lt;/blockquote&gt;
Did you read the Press Releases that came out of the Jabber Foundation? Of course they are working on this. And if Google's policy of releasing products first and standards second then these developments should be right around the corner. Google Talk and Jingle will dominate in 2006. Read more here:

http://www.voipwiki.com/blog/?p=10</description>
		<content:encoded><![CDATA[	<blockquote><p> I don’t see any major threat to any of the existing VoIP clients anytime soon. At least not until Google can figure out a way to provide other compatible VoIP clients connectivity to PSTN networks at a price-point comparable to Skype, Yahoo, and the rest of the gang.</p></blockquote>
	<p>Did you read the Press Releases that came out of the Jabber Foundation? Of course they are working on this. And if Google&#8217;s policy of releasing products first and standards second then these developments should be right around the corner. Google Talk and Jingle will dominate in 2006. Read more here:</p>
	<p><a href='http://www.voipwiki.com/blog/?p=10' rel='nofollow'>http://www.voipwiki.com/blog/?p=10</a>
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Google Talk Ups the Ante by: VoIPWiki Blog &#187; 2006 – The Year to Jabber and Jingle</title>
		<link>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-78</link>
		<pubDate>Wed, 04 Jan 2006 14:09:34 +0000</pubDate>
		<guid>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-78</guid>
					<description>[...] People who downplay Jingle’s impact on the industry and maintain that SIP will continue to dominate 2006 are missing the bigger picture. First, SIP is NOT the most dominant VoIP protocol: Skype is. The Skype protocol accounts for over 45% of the VoIP traffic in the United States and probably even more on a global basis. Any protocol that grows at a rate faster than Skype with the capacity to unseat it as the leading VoIP protocol will definitely dominate 2006. [...]</description>
		<content:encoded><![CDATA[	<p>[&#8230;] People who downplay Jingle’s impact on the industry and maintain that SIP will continue to dominate 2006 are missing the bigger picture. First, SIP is NOT the most dominant VoIP protocol: Skype is. The Skype protocol accounts for over 45% of the VoIP traffic in the United States and probably even more on a global basis. Any protocol that grows at a rate faster than Skype with the capacity to unseat it as the leading VoIP protocol will definitely dominate 2006. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Google Talk Ups the Ante by: David G</title>
		<link>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-45</link>
		<pubDate>Tue, 20 Dec 2005 04:13:03 +0000</pubDate>
		<guid>http://www.jason.netrino.com/weblog/2005/12/18/google-talk-ups-the-ante/#comment-45</guid>
					<description>Excellent post,

Yours is the most accurate review comparing both API's that I've read, nice one, thanks!

Despite being proprietary, I'd add that the SKYPE API is (counter-intuitively)  more accessible to developers looking to rapidly develop working applications - the SKYPE documentation is solid, complete and uncomplicated, and has ample cross-platform support &amp;#38; sample code. 

I had a working application running against the skype API in </description>
		<content:encoded><![CDATA[	<p>Excellent post,</p>
	<p>Yours is the most accurate review comparing both API&#8217;s that I&#8217;ve read, nice one, thanks!</p>
	<p>Despite being proprietary, I&#8217;d add that the SKYPE API is (counter-intuitively)  more accessible to developers looking to rapidly develop working applications - the SKYPE documentation is solid, complete and uncomplicated, and has ample cross-platform support &amp; sample code. </p>
	<p>I had a working application running against the skype API in
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
