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 13:00:37 +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: <E1AE744A-5598-412F-A3FB-92D70B43A664@cisco.com>

Hmm - seem to me most of theses should be mandatory too

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

> Mandatory API for Media Capture and Streams API
> 
> Mandator API
> MediaStream:
>  
> id;
> getAudioTracks ();
> getVideoTracks ();
> addTrack ();
> removeTrack ();
>  
> MediaStreamTrack:
>  
> getSourceInfos ();
> constraints ();
> capabilities ();
> applyConstraints ();
> stop ();
> getUserMedia ();
>  
> DOMString             kind;
> DOMString             id;
> boolean               remote;
> Optional API
> MediaStream:
>  
> getTrackById ();
> clone ();
> DOMString             label;
>  
> MediaStreamTrack:
>  
> states ();
> clone ();
> boolean               enabled;
> boolean               muted;
> boolean               _readonly;
> MediaStreamTrackState readyState;
> 
> EventHandlers and callbacks are yet to be updated
> 
> 
> 
> 
> Thanks,
> 
> 
> 
> Kiran.
> 
> 
> On Mon, Mar 10, 2014 at 4:34 PM, Kiran Kumar <g.kiranreddy4u@gmail.com> wrote:
> Hi,
> As discussed,  I prepared the following list for webrtc API.
> 
> Mandator API
> createOffer ();
> createAnswer ();
> setLocalDescription ();
> setRemoteDescription ();
> updateIce ();
> addIceCandidate ();
> getLocalStreams ();
> getRemoteStreams ();
> addStream ();
> removeStream ();
> close ();
> createDataChannel ();
> insertDTMF ();
> getStats ();
>  
> RTCSessionDescription? localDescription;
> 
> RTCSessionDescription? remoteDescription;
> 
> Optional API
> 
> getStreamById ();
> RTCSignalingState      signalingState;
> RTCIceGatheringState   iceGatheringState;
> RTCIceConnectionState  iceConnectionState;
> boolean          canInsertDTMF;
> DOMString        toneBuffer;
> long             duration;
> long             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 13:01:12 UTC

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