This repository was archived by the owner on Feb 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Feb 25, 2026. It is now read-only.
getStats interface #82
Description
Activity
Might be even better as a Promise result, but I like it.
I think that duck-typing is likely to be better, as in:
interface RTCStatsSource { Promise<RTCStats> getStats(); }; interface RTCRtpSender implements RTCStatsSource;How about this?
typedef (RTCRtpSender or RTCRtpReceiver or RTCDtlsTransport or RTCIceTransport or RTCSctpTransport) RTCStatsObject;
interface RTCStats {
Promise getStats (RTCStatsObject object, RTCStatsCallback successCallback, RTCErrorCallback failureCallback);
};- added a commit that references this issue
on May 14, 2014 Stats are still a mess in current spec. I like the way martin did it.
Shijun's proposal added in the latest editor's draft:
http://ortc.org/wp-content/uploads/2014/06/ortc.html
From Shijun Sun:
I’ve been thinking more about the getStats() interface.
One possible way to separate it from other objects is probably to define it as
Interface RTCStats{
void getStats(object, success_callback, failure_callback);
}
The “object” can be RtpSender, RtpReceiver, IceTransport, DtslTransport, SdesTransport, etc. and can be extended without changing other existing objects.