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 <notifications@github.com> wrote: > Also, do we make the caching explicit in the RTCRtpContributingSource > description or let it be implied by descriptions elsewhere (#1111 > <https://github.com/w3c/webrtc-pc/issues/1111>)? > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/webrtc-pc/issues/1117#issuecomment-292472454>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ANdux9vrOCyNcDMyPI6ZK_hlPhKPenCXks5rtfDkgaJpZM4M2lyG> > . > -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1117#issuecomment-292591892 using your GitHub accountReceived on Friday, 7 April 2017 16:57:17 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:40 UTC