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

per-DataChannel stats: on PeerConnection or on DataChannel?

From: Peter Thatcher <pthatcher@google.com>
Date: Thu, 18 Dec 2014 12:20:10 -0800
Message-ID: <CAJrXDUE9rbpZzUoa4=5N_f+1bGbGJYo_=kOiS1r48_w6QFx0_w@mail.gmail.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Cc: Donald Curtis <decurtis@google.com>
​In the current WebRTC draft, we have:

partial interface RTCPeerConnection {
    void getStats (MediaStreamTrack? selector, RTCStatsCallback
successCallback, RTCPeerConnectionErrorCallback failureCallback);
}

To add the ability to get stats about a particular RTCDataChannel do we
want to have

A.  ​PeerConnection.getStats(RTCDataChannel, ..., ...), like so:

partial interface RTCPeerConnection {
    void getStats (RTCDataChannel? selector, RTCStatsCallback
successCallback, RTCPeerConnectionErrorCallback failureCallback);
}


or


B.  RTCDataChannel.getStats(..., ...) like so:



partial interface RTCDataChannel {
    void getStats (RTCStatsCallback successCallback,
RTCPeerConnectionErrorCallback failureCallback);
}



I prefer B.  LIkewise, I think it makes sense to eventually have
RtpSender.getStats, DtlsTransport.getStats, and IceTransport.getStats.
That way, the browser doesn't have to gather stats about everything to get
stats about something, and we don't have to add a new
PeerConnection.getStats overload for every single new object we add.


Has there already been discussion about this that I don't remember?
Received on Thursday, 18 December 2014 20:21:23 UTC

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