Closed Bug 1217920 Opened 9 years ago Closed 7 years ago

getStats: remoteId has been renamed to associateStatsId

Categories

(Core :: WebRTC, defect, P1)

Product:
Core
Component:
WebRTC
Version:
42 Branch
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: fippo, Assigned: ng)

References

(Blocks 1 open bug,
URL
)

Details

In the stats sample, I get the following report:
  Report 0
  time 1445619753610.147
  type inboundrtp
  id: outbound_rtcp_video_1
  isRemote: true
  mediaType: video
  remoteId: outbound_rtp_video_1
  ssrc: 3240370319
  bytesReceived: 587340
  jitter: 0.529
  mozRtt: 1
  packetsLost: 0
  packetsReceived: 753

This has a remoteId which should be named associatedStatsId per spec-issue here: https://github.com/w3c/webrtc-stats/issues/17

Note that currently the peerconnection spec still shows remoteId, will file issues for that.
Blocks: webrtc_spec
backlog: --- → webrtc/webaudio+
Rank: 35
Priority: -- → P3
Summary: getStats: remoteId has been renamed to associatedStats → getStats: remoteId has been renamed to associateStatsId
Giving this one a bump, now that Chrome is near having a spec compliant stats.
Rank: 35 → 19
Priority: P3 → P1
Assignee: jib → na-g
Need info on self, to check if this needs to be closed.

Waiting on the resolution of Jan-Ivar's refactor out of isRemote[1] which restores remoteId to the spec.
[1] https://github.com/w3c/webrtc-stats/pull/191
Flags: needinfo?(na-g)
Spec has reverted to remoteId [1], so this is now invalid.

[1] https://github.com/w3c/webrtc-stats/pull/191
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Flags: needinfo?(na-g)
You need to log in before you can comment on or make changes to this bug.