- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Nov 2014 18:16:51 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27213
Harald Alvestrand <harald@alvestrand.no> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |25497
--- Comment #1 from Harald Alvestrand <harald@alvestrand.no> ---
>From Peter Thatcher:
At TPAC 2014, we realized that now that we have RtpSender, we don't need a
DTMFSender to be tied to a track. We can tie it to an RtpSender instead, and
that would clean things up a fair bit.
Based on that, I propose we:
1. Remove RTCPeerConnection.createDTMFSender
2. Add RTCRtpSender.dtmf, of type "RTCDTMFSender?".
3. Remove RTCDTMFSender.canInsertDTMF and RTCDTMFSender.track.
The rule is: If RtpSender.dtmf is non-null, you can send DTMF. Here is an
example:
var pc = ...;
var track = ...;
var rtpSender = pc.addTrack(track);
if (rtpSender.dtmf) {
rtpSender.dtmf.insertDTMF(...);
}
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 4 November 2014 18:16:52 UTC