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

Re: Futures in WebRTC

From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 4 Jun 2013 08:57:54 -0700
Message-ID: <CABcZeBNoZwcLnj3B1CH2d5UMz=CodhmJ5R_qFJ111mgUeLnVTw@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On Tue, Jun 4, 2013 at 8:39 AM, cowwoc <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?

Received on Tuesday, 4 June 2013 15:59:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:44 UTC