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 16:34:59 +0530
Message-ID: <CAGW1TF7CEBTUqicAz53EXOSbBnFvkag_60ns4YavhAochdCv9w@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,
As discussed,  I prepared the following list for webrtc API.

*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>
();



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*

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>
;

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>
;


 EventHandlers and callbacks are yet to be updated.

Let me know your ideas and views to improve this.


Thanks,

Kiran.



On Thu, Jan 30, 2014 at 7:26 AM, Kiran Kumar <g.kiranreddy4u@gmail.com>wrote:

> +1 for it to be in spec.
> If everyone agrees for it, I am happy to work on it.
>
> Thanks,
> Kiran.
>
>
> On Thu, Jan 30, 2014 at 6:42 AM, Cullen Jennings (fluffy) <
> fluffy@cisco.com> wrote:
>
>>
>> I think that needs to be (and hopefully is in) the specs.
>>
>>
>> On Jan 28, 2014, at 7:05 AM, Kiran Kumar <g.kiranreddy4u@gmail.com>
>> wrote:
>>
>> > Dear All,
>> > Is there any plan to specification or wiki page to know which API's of
>> webrtc and mediacapture specs are mandatory to implement in a browser and
>> which of those are optional.
>> >
>> > Thanks,
>> > Kiran.
>>
>>
>
Received on Monday, 10 March 2014 11:06:16 UTC

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