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

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

From: Kiran Kumar <g.kiranreddy4u@gmail.com>
Date: Mon, 10 Mar 2014 18:40:28 +0530
Message-ID: <CAGW1TF7F=2qWKtcWmtdcWU9URyUmGXYTfjt=v11zu_Jg-iyv8g@mail.gmail.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Hi,
Please find the updated list modified as per the comments.

I think It would be better update the list in a wiki page instead of the
mail chain.

*Mandator API*

createOffer<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-createOffer-void-RTCSessionDescriptionCallback-successCallback-RTCPeerConnectionErrorCallback-failureCallback-MediaConstraints-constraints>();

createAnswer<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-createAnswer-void-RTCSessionDescriptionCallback-successCallback-RTCPeerConnectionErrorCallback-failureCallback-MediaConstraints-constraints>();

setLocalDescription<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-setLocalDescription-void-RTCSessionDescription-description-VoidFunction-successCallback-RTCPeerConnectionErrorCallback-failureCallback>();

setRemoteDescription<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-setRemoteDescription-void-RTCSessionDescription-description-VoidFunction-successCallback-RTCPeerConnectionErrorCallback-failureCallback>();

updateIce<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-updateIce-void-RTCConfiguration-configuration-MediaConstraints-constraints>();

addIceCandidate<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-addIceCandidate-void-RTCIceCandidate-candidate-VoidFunction-successCallback-RTCPeerConnectionErrorCallback-failureCallback>();

getLocalStreams<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-getLocalStreams-sequence-MediaStream>();

getRemoteStreams<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-getRemoteStreams-sequence-MediaStream>();

addStream<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-addStream-void-MediaStream-stream-MediaConstraints-constraints>();

removeStream<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-removeStream-void-MediaStream-stream>();

close <http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-close-void> ();

createDataChannel
<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-createDataChannel-RTCDataChannel-DOMString-label-RTCDataChannelInit-dataChannelDict>
();

insertDTMF <http://www.w3.org/TR/webrtc/#widl-RTCDTMFSender-insertDTMF-void-DOMString-tones-long-duration-long-interToneGap>
();

getStats <http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-getStats-void-MediaStreamTrack-selector-RTCStatsCallback-successCallback-RTCPeerConnectionErrorCallback-failureCallback>
();

getStreamById<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-getStreamById-MediaStream-DOMString-streamId>();



RTCSignalingState <http://www.w3.org/TR/webrtc/#idl-def-RTCSignalingState>
signalingState<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-signalingState>
;

RTCIceGatheringState<http://www.w3.org/TR/webrtc/#idl-def-RTCIceGatheringState>
iceGatheringState<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-iceGatheringState>
;

RTCIceConnectionState<http://www.w3.org/TR/webrtc/#idl-def-RTCIceConnectionState>
iceConnectionState<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-iceConnectionState>
;

RTCSessionDescription<http://www.w3.org/TR/webrtc/#idl-def-RTCSessionDescription>?
localDescription<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-localDescription>
;

RTCSessionDescription<http://www.w3.org/TR/webrtc/#idl-def-RTCSessionDescription>?
remoteDescription<http://www.w3.org/TR/webrtc/#widl-RTCPeerConnection-remoteDescription>
;


*Optional API*


boolean          canInsertDTMF
<http://www.w3.org/TR/webrtc/#widl-RTCDTMFSender-canInsertDTMF>;

DOMString        toneBuffer
<http://www.w3.org/TR/webrtc/#widl-RTCDTMFSender-toneBuffer>;

long             duration
<http://www.w3.org/TR/webrtc/#widl-RTCDTMFSender-duration>;

long             interToneGap
<http://www.w3.org/TR/webrtc/#widl-RTCDTMFSender-interToneGap>;


Thanks,
Kiran.


On Mon, Mar 10, 2014 at 6:29 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote:

>
> 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 13:11:16 UTC

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