<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tokbox embraces WebRTC to give developers access to Flash-free video chat</title>
	<atom:link href="http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/</link>
	<description></description>
	<lastBuildDate>Sun, 19 May 2013 03:33:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Tsahi Levent-Levi</title>
		<link>http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/#comment-878118</link>
		<dc:creator><![CDATA[Tsahi Levent-Levi]]></dc:creator>
		<pubDate>Wed, 08 Aug 2012 05:54:33 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=550545#comment-878118</guid>
		<description><![CDATA[Janko,

WebRTC is the way to go in the future video calling scene for browsers.
Today, companies need to invest their time and effort in Flash for such services (as TokBox and others have done), but within a year or two they will need to shift to WebRTC.

TokBox has an issue here that I am not sure how they solve. WebRTC uses VP8 while Flash uses H.264. This means they need to transcode the video for all sessions that have participants with both technologies. If this is the case, then this is costing them a small fortune on the server side.]]></description>
		<content:encoded><![CDATA[<p>Janko,</p>
<p>WebRTC is the way to go in the future video calling scene for browsers.<br />
Today, companies need to invest their time and effort in Flash for such services (as TokBox and others have done), but within a year or two they will need to shift to WebRTC.</p>
<p>TokBox has an issue here that I am not sure how they solve. WebRTC uses VP8 while Flash uses H.264. This means they need to transcode the video for all sessions that have participants with both technologies. If this is the case, then this is costing them a small fortune on the server side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Ed</title>
		<link>http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/#comment-877612</link>
		<dc:creator><![CDATA[Rick Ed]]></dc:creator>
		<pubDate>Tue, 07 Aug 2012 19:14:58 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=550545#comment-877612</guid>
		<description><![CDATA[This &quot;lets kill flash&quot; union of bozos is really getting old, plus, how is it good to kill flash video by replacing it with something closed and locked in. Better go with webRTC.io than this me-too-closed API.]]></description>
		<content:encoded><![CDATA[<p>This &#8220;lets kill flash&#8221; union of bozos is really getting old, plus, how is it good to kill flash video by replacing it with something closed and locked in. Better go with webRTC.io than this me-too-closed API.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fersho311</title>
		<link>http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/#comment-877471</link>
		<dc:creator><![CDATA[fersho311]]></dc:creator>
		<pubDate>Tue, 07 Aug 2012 17:26:35 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=550545#comment-877471</guid>
		<description><![CDATA[I love WebRTC]]></description>
		<content:encoded><![CDATA[<p>I love WebRTC</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Naga Harish Movva</title>
		<link>http://gigaom.com/2012/08/07/tokbox-opentok-webrtc/#comment-877416</link>
		<dc:creator><![CDATA[Naga Harish Movva]]></dc:creator>
		<pubDate>Tue, 07 Aug 2012 16:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=550545#comment-877416</guid>
		<description><![CDATA[Superb!]]></description>
		<content:encoded><![CDATA[<p>Superb!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
