Issue 230: Stats API: getStats on the IceGatherer??

>From Philipp Hancke:

getStats on the IceGatherer doesn't make much sense to me. Everything interesting (candidate pairs) will happen on the IceTransport. Now the IceTransport knows about remote candidates but (technically) not about local candidates. But that means that the candidate pair from the transport references local candidate ids which need to be obtained from a getStats call to the ice gatherer.
So if the icetransport knows the local candidate ids, can't it just proxy stats for them?

Received on Monday, 31 August 2015 18:20:23 UTC