Re: [webrtc-pc] RTCRtpContributingSource.getReceiver()

In my opinion, the caching and internal references between objects should
be left as an implementation detail. Other implementers could choose
different approaches. And purely from an API perspective, a "getReceiver"
method doesn't really buy anything, since the application should already
know which receiver it got a contributing source from.

On Fri, Apr 7, 2017 at 1:16 AM, henbos <> wrote:

> Also, do we make the caching explicit in the RTCRtpContributingSource
> description or let it be implied by descriptions elsewhere (#1111
> <>)?
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <>, or mute
> the thread
> <>
> .

GitHub Notification of comment by taylor-b
Please view or discuss this issue at using your GitHub account

Received on Friday, 7 April 2017 16:57:17 UTC