- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Jul 2018 08:09:33 +0000
- To: public-webrtc-logs@w3.org
If we have a track attribute we should have a streams attribute. Why obscure this part of the state to only be seen in events firing? Whether you want to shim getLocal/RemoteStreams() or you want to do the 1.0 equivalent of those APIs - you want to iterate the PCs streams - this allows you to do that without keeping a map of receiver -> streams that you update on events firing and on any edge case where the slot might be cleared. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1944#issuecomment-408013887 using your GitHub account
Received on Thursday, 26 July 2018 08:09:44 UTC