W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

RE: VS: Teleco Integrators vs Web Developers vs Browser Implementers

From: Martin Steinmann <martin@ezuce.com>
Date: Fri, 5 Jul 2013 13:40:06 -0400
To: "'Robin Raymond'" <robin@hookflash.com>
Cc: "'public-webrtc_w3.org'" <public-webrtc@w3.org>
Message-ID: <034601ce79a6$b0625750$112705f0$@ezuce.com>
>From: Robin Raymond [mailto:robin@hookflash.com] 
>Sent: Friday, July 05, 2013 1:25 PM
>To: Martin Steinmann
>Cc: 'public-webrtc_w3.org'
>Subject: RE: VS: Teleco Integrators vs Web Developers vs Browser
Implementers

> 

>
>We already have an API that is very much disagreed upon by those of us
actually trying to use it now!
>
>-Robin

. meaning for those implementing P2P and other proprietary protocols such as
Open Peer.  It should not be about browser to browser, but browser to any
and a standardization process like this is ill-suited to accommodate leading
edge experiments with new protocols.

--martin

 





 
 
If you want to solve 'world hunger' you will likely never get to any API
anyone will agree with.  What I would suggest is that the group gets back to
focus.  The primary application is voice and video at least in my book and
the standard protocols for that are SIP and XMPP and I haven't heard
anything to the contrary on this list.  Avoiding gateways and media
anchoring points and enable seamless enterprise interop between different
devices might cost you a few more bits on the wire or a bit more complexity
for your proprietary app, but so be it.  Otherwise, create your own browser
plugin and you can do whatever.
--martin
 
 
Received on Friday, 5 July 2013 17:40:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:34 UTC