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

Hi,
Some time back I raised this question [1] regarding this.
I am not preparing this list for the final specification. It is just a
reference like what are API are stable and mandatory according to the
present published version.

Since spec is not finalized, Some API which are specified as mandatory in
one version, are very rapidly changing to the next.
It is confusing that which API of the present version of draft are
mandatory and which are not (not in my sense, even though we don't
implement those API also, we can achieve interoperability).

This can guide the people implementing the browser platform to give
priority.


[1]
http://lists.w3.org/Archives/Public/public-media-capture/2014Jan/0043.html





On Mon, Mar 10, 2014 at 7:07 PM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> I'm a bit confused.
>
> What is the reason why you're proposing to make parts of the APIs that
> are now specced as mandatory to support optional at this stage in the work?
>
> Stefan
>
> On 2014-03-10 14:11, Kiran Kumar wrote:
> > 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 <mailto:fluffy@cisco.com>> wrote:
> >
> >
> >     Few comments
> >
> >     On Mar 10, 2014, at 5:04 AM, Kiran Kumar <g.kiranreddy4u@gmail.com
> >     <mailto: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.
> >
> >
> >
> >
> >
>
>