- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Fri, 03 Aug 2012 17:01:10 -0700
- To: public-webrtc@w3.org
(wearing my co-Chair hat) I've discussed this with several people at the IETF meeting. Unless someone raises an objection, the chairs will instruct the editors to make this change. On 08/03/2012 04:57 PM, bugzilla@jessica.w3.org wrote: > https://www.w3.org/Bugs/Public/show_bug.cgi?id=18485 > > Summary: Change DTMF API to be on PeerConnection > Product: WebRTC Working Group > Version: unspecified > Platform: PC > OS/Version: Linux > Status: NEW > Severity: normal > Priority: P2 > Component: WebRTC API > AssignedTo: public-webrtc@w3.org > ReportedBy: harald@alvestrand.no > CC: public-webrtc@w3.org > > > Implementing the proposed DTMF API has turned out to be surprisingly complex > compared to the importance of the feature; the typing requirements for > MediaStream seem to be heavily complicated by it. > > Tommy Widenflycht has suggested instead that we define calls to make available: > > pc.canSendDTMF(MediaStreamTrack) > pc.sendDTMF(MediaStreamTrack, tones, duration) > > This has no impact on the definition of MediaStream and allows implementation > of sendDTMF without touching anything but PeerConnection. >
Received on Saturday, 4 August 2012 00:01:35 UTC