Add API to report "interesting" usage patterns to PC client
Bug: chromium:866792 Change-Id: Ic8bec5494aaa617c833c90be2b912f7367b44929 Reviewed-on: https://webrtc-review.googlesource.com/90246 Commit-Queue: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Steve Anton <steveanton@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24111}
This commit is contained in:
committed by
Commit Bot
parent
6031e69d34
commit
c0e9725916
@ -1098,6 +1098,14 @@ class PeerConnectionObserver {
|
||||
// TODO(hbos,deadbeef): Make pure virtual when all subclasses implement it.
|
||||
virtual void OnRemoveTrack(
|
||||
rtc::scoped_refptr<RtpReceiverInterface> receiver) {}
|
||||
|
||||
// Called when an interesting usage is detected by WebRTC.
|
||||
// An appropriate action is to add information about the context of the
|
||||
// PeerConnection and write the event to some kind of "interesting events"
|
||||
// log function.
|
||||
// The heuristics for defining what constitutes "interesting" are
|
||||
// implementation-defined.
|
||||
virtual void OnInterestingUsage(int usage_pattern) {}
|
||||
};
|
||||
|
||||
// PeerConnectionDependencies holds all of PeerConnections dependencies.
|
||||
|
||||
Reference in New Issue
Block a user