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

Re: Futures in WebRTC

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Tue, 04 Jun 2013 11:59:59 -0400
Message-ID: <51AE0EFF.6030308@bbs.darktech.org>
To: Eric Rescorla <ekr@rtfm.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 04/06/2013 11:57 AM, Eric Rescorla wrote:
> On Tue, Jun 4, 2013 at 8:39 AM, cowwoc <cowwoc@bbs.darktech.org 
> <mailto:cowwoc@bbs.darktech.org>> wrote:
>
>         As an end-user, using DOM Futures was as simple as including
>     the Polyfill JS. Thing is, if WebRTC is built into the browser,
>     I'm guessing users would expect all dependencies (i.e. DOM
>     Futures) to be built-in too.
>
>         Seeing as the polyfill JS is rather small. What prevents you
>     vendors from folding this into the browser at the same time as WebRTC
>
>
> Conversely, what prevents anyone who wishes to use a futures interface
> from loading their own WebRTC Futures wrapper?
>
> -Ekr

     Nothing, I guess, but it would be nice if this wrapper were 
officially sanctioned and maintained by the standard. You could start 
out this way and drop the legacy API (with callbacks) once you have a 
better understanding of when vendors will implement DOM Futures.

Gili
Received on Tuesday, 4 June 2013 16:01:29 UTC

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