doubango and WebRTC
132 views
Skip to first unread message
cybion
Jun 23, 2011, 2:03:33 AM6/23/11
to Doubango
Hello,
Seems Google is pushing real time web collaboration in the browser ,
on top of Webkit which is almost universal ( safari, chrome, webos
browser , ..... )
WebRTC is the name of their solution.
What about the connexions between doubango and WebRTC ?
Will we see some time the possibility of contacting somebody with an
Android platform without leaving the browser ? and with no plug-in
inside ?
I saw that Idoubs now supports WebM and Iblc . What is next in the
roadmap ?
Can we help ?
Best
David Menga
Seems Google is pushing real time web collaboration in the browser ,
on top of Webkit which is almost universal ( safari, chrome, webos
browser , ..... )
WebRTC is the name of their solution.
What about the connexions between doubango and WebRTC ?
Will we see some time the possibility of contacting somebody with an
Android platform without leaving the browser ? and with no plug-in
inside ?
I saw that Idoubs now supports WebM and Iblc . What is next in the
roadmap ?
Can we help ?
Best
David Menga
Mamadou
Jun 23, 2011, 3:47:48 AM6/23/11
to Doubango
For me, webrtc is far from being ready.
iDoubs doesn't support WebM but VP8 is in our roadmap.
1. you need a modified version of webkit
2. even if webkit is used by safari, webos, firefox ... I don't think
that Apple, Mozilla ... will accept to get this part of the code.
There is a war between Apple+Microsoft vs Google on the codec to use
in HTML5 (H.264 vs VP8).
a) Apple knows that supporting webrtc in safari will help Google to
make VP8 a standard de facto. Same for iLBC (Global IP Solutions is
now part of Google)
b) Microsoft knows that webrtc will be a direct concurrent for Skype
and they will try to make Google's life harder by for example not
allowing webrtc to open UDP port on Windows.
3. the last version of webrtc was only stable on Linux
4. you still needs to develop SIP/XMPP/... gateways likes what is done
with flash. webrtc only provides the signaling channel+state machine
and it's up to you to implement the protocol.
5. ... to be continued
Doubango is a plugin-based framework which means that you can easily
replace the media plugins with webrtc
iDoubs doesn't support WebM but VP8 is in our roadmap.
1. you need a modified version of webkit
2. even if webkit is used by safari, webos, firefox ... I don't think
that Apple, Mozilla ... will accept to get this part of the code.
There is a war between Apple+Microsoft vs Google on the codec to use
in HTML5 (H.264 vs VP8).
a) Apple knows that supporting webrtc in safari will help Google to
make VP8 a standard de facto. Same for iLBC (Global IP Solutions is
now part of Google)
b) Microsoft knows that webrtc will be a direct concurrent for Skype
and they will try to make Google's life harder by for example not
allowing webrtc to open UDP port on Windows.
3. the last version of webrtc was only stable on Linux
4. you still needs to develop SIP/XMPP/... gateways likes what is done
with flash. webrtc only provides the signaling channel+state machine
and it's up to you to implement the protocol.
5. ... to be continued
Doubango is a plugin-based framework which means that you can easily
replace the media plugins with webrtc
Emmanuel BUU
Jun 23, 2011, 10:38:58 PM6/23/11
to doub...@googlegroups.com
Hello,
From our point of view, WebRTC is an attempt to reimplement in Javascript a feature provided by Flash 10 and Flash Media Server.
While it is interesting as an API, we do not beleive that the protocols and codecs chosen to support it are good candidates: they simply don't
care about interoperabiity with other services and providers.
Emmanuel BUU
IVèS
http://www.ives.fr/
Le 23/06/11 09:47, Mamadou a écrit :
From our point of view, WebRTC is an attempt to reimplement in Javascript a feature provided by Flash 10 and Flash Media Server.
While it is interesting as an API, we do not beleive that the protocols and codecs chosen to support it are good candidates: they simply don't
care about interoperabiity with other services and providers.
- Although RTP is used, audio in ILBC and Video in VP8 is not exactly the most widespead supported codec in the videotelephony world. We would have perferred to see H.264 for video but as Mamadou mentioned, Google is not neutral here and has stakes in the process
- WOrse: the signalling is just another proprietary protocol.
Where is the interop with SIP or at least Jingle that Google
fostered?
Emmanuel BUU
IVèS
http://www.ives.fr/
Le 23/06/11 09:47, Mamadou a écrit :
Reply all
Reply to author
Forward
0 new messages