W3C home > Mailing lists > Public > public-webrtc@w3.org > December 2011

Re: DTMF again

From: Timothy B. Terriberry <tterriberry@mozilla.com>
Date: Thu, 15 Dec 2011 00:04:12 -0800
Message-ID: <4EE9A9FC.80401@mozilla.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
> telephone-event). Harald had suggested that the DTMF API only be present
> on a stream if that stream supports DTMF, but I'd like to get more
> feedback from others (especially folks with WebIDL experience) on that
> approach.

The question raised on the call was whether or not this is something 
that can change during the lifetime of a MediaStream. I had a chat about 
this with Boris Zbarsky. He says it's relatively hard to do something 
like this for us because of the way our DOM bindings for ECMAScript 
work, unless the object is actually a special kind of object (e.g., 
MediaStreamWithDTMF), and that while APIs appearing might be marginally 
acceptable, APIs disappearing is pretty bad form.

As far as I understand O/A, the remote side can revise its offer or 
answer to add or remove support for a DTMF codec at any time (though I 
would not typically expect it to do so), so this seems like a problem.
Received on Thursday, 15 December 2011 08:04:37 UTC

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