Re: Issue 148: Success & Failure Callbacks in RTCRtpSender.setTrack from Peter Thatcher on 2014-09-03 (public-ortc@w3.org from September 2014)

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 3 Sep 2014 11:10:04 -0700
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: "public-ortc@w3.org" <public-ortc@w3.org>
Message-ID: <CAJrXDUEdsz1B6rcCC3f5owSiLMtixvws==Q9owfRPPpy0zXHBg@mail.gmail.com>

If it could fail, then we'd need a callback.  If it can't, then we
don't.  I'd prefer a Promise to two callbacks.

On Wed, Sep 3, 2014 at 9:59 AM, Bernard Aboba
<Bernard.Aboba@microsoft.com> wrote:
> >From Jan-Ivar Bruaroey <jib@mozilla.com>:
>
> Proposal for RTCRtpSender.replaceTrack method:
> http://lists.w3.org/Archives/Public/public-webrtc/2014Sep/0001.html
>
> Difference from RTCRtpSender.setTrack is use of a success and failure callback.
>
> Is this necessary, and if so, could it be a Promise?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>

Received on Wednesday, 3 September 2014 18:11:40 UTC