W3C home > Mailing lists > Public > public-webrtc@w3.org > March 2014

Re: Question about mandatory API in webrtc and mediacapture specs.

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Mon, 10 Mar 2014 12:59:08 +0000
To: Kiran Kumar <g.kiranreddy4u@gmail.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <B3BFE00D-CF59-456D-A4D1-E931764C10AD@cisco.com>

Few comments

On Mar 10, 2014, at 5:04 AM, Kiran Kumar <g.kiranreddy4u@gmail.com> wrote:

> getStreamById ();
> RTCSignalingState      signalingState;
> RTCIceGatheringState   iceGatheringState;
> RTCIceConnectionState  iceConnectionState;

I think all the above have to Mandatory or else you canít really build apps that deal with error. They are also no big deal to implement because  the other mandatory stuff means you more or less need to have this state internally. 

> boolean          canInsertDTMF;
> 

Even if DTMF is optional, I think you need the above boolean as madotory so applications can find out if they are on a browser that supports DTMF or not. 

That said, I think DTMF support should be MTI but I can see that one being argued either way. 
Received on Monday, 10 March 2014 12:59:36 UTC

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