Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(837)

Issue 2565463002: RTCIceCandidatePairStats.requestsReceived defined by RTCStatsCollector. (Closed)

Created:
4 years ago by hbos
Modified:
4 years ago
CC:
webrtc-reviews_webrtc.org, the sun, tterriberry_mozilla.com
Target Ref:
refs/pending/heads/master
Project:
webrtc
Visibility:
Public.

Description

RTCIceCandidatePairStats.requestsReceived defined by RTCStatsCollector. Spec: https://w3c.github.io/webrtc-stats/#dom-rtcicecandidatepairstats-requestsreceived BUG=chromium:633550 Committed: https://crrev.com/d82f5125b7cc00ddd16430b0d4e1f8cfde51ac17 Cr-Commit-Position: refs/heads/master@{#15506}

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+5 lines, -2 lines) Patch
M webrtc/api/rtcstats_integrationtest.cc View 1 chunk +1 line, -1 line 0 comments Download
M webrtc/api/rtcstatscollector.cc View 1 chunk +2 lines, -0 lines 1 comment Download
M webrtc/api/rtcstatscollector_unittest.cc View 2 chunks +2 lines, -0 lines 0 comments Download
M webrtc/api/stats/rtcstats_objects.h View 1 chunk +0 lines, -1 line 0 comments Download

Messages

Total messages: 19 (9 generated)
hbos
Please take a look, deadbeef & hta
4 years ago (2016-12-08 14:55:13 UTC) #4
hbos
https://codereview.webrtc.org/2565463002/diff/1/webrtc/api/rtcstatscollector.cc File webrtc/api/rtcstatscollector.cc (right): https://codereview.webrtc.org/2565463002/diff/1/webrtc/api/rtcstatscollector.cc#newcode638 webrtc/api/rtcstatscollector.cc:638: static_cast<uint64_t>(info.recv_ping_requests); This is what the old getStats uses for ...
4 years ago (2016-12-08 14:59:37 UTC) #5
Taylor Brandstetter
I'm still not clear on how we're supposed to differentiate connectivity requests from consent requests, ...
4 years ago (2016-12-08 21:36:10 UTC) #8
Taylor Brandstetter
On 2016/12/08 21:36:10, Taylor Brandstetter wrote: > I'm still not clear on how we're supposed ...
4 years ago (2016-12-08 22:02:24 UTC) #9
hta-webrtc
lgtm
4 years ago (2016-12-09 09:50:36 UTC) #10
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/2565463002/1
4 years ago (2016-12-09 12:10:40 UTC) #12
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years ago (2016-12-09 12:12:42 UTC) #15
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/d82f5125b7cc00ddd16430b0d4e1f8cfde51ac17 Cr-Commit-Position: refs/heads/master@{#15506}
4 years ago (2016-12-09 12:12:49 UTC) #17
hbos
On 2016/12/08 22:02:24, Taylor Brandstetter wrote: > On 2016/12/08 21:36:10, Taylor Brandstetter wrote: > > ...
4 years ago (2016-12-09 12:42:20 UTC) #18
hta-webrtc
4 years ago (2016-12-09 13:42:15 UTC) #19
Message was sent while issue was closed.
On 2016/12/09 12:42:20, hbos wrote:
> On 2016/12/08 22:02:24, Taylor Brandstetter wrote:
> > On 2016/12/08 21:36:10, Taylor Brandstetter wrote:
> > > I'm still not clear on how we're supposed to differentiate connectivity
> > requests
> > > from consent requests, but for now this is better than nothing. lgtm
> > 
> > Here's an issue I filed for this, by the way:
> > https://github.com/w3c/webrtc-stats/issues/96
> 
> Meaning we now have a bug that requestsReceived will keep incrementing after
> connection has been established, when it's suppose to stop incrementing and
> start incrementing consentRequestsReceived instead. Correct?

https://github.com/w3c/webrtc-stats/issues/96 tracks trying to clarify this in
the spec.

Powered by Google App Engine
This is Rietveld 408576698