W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2018

[webrtc-pc] Unable to figure out which receivers are "active".

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Fri, 29 Jun 2018 08:25:54 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-336908734-1530260752-sysbot+gh@w3.org>
henbos has just created a new issue for https://github.com/w3c/webrtc-pc:

== Unable to figure out which receivers are "active". ==
Based on discussions at #1890, we are unable to figure out which receivers are "active" or not after setRemoteDescription().
1. const offer = await caller.createOffer();
2. await caller.setLocalDescription(offer);
3. await callee.setRemoteDescription(offer);
4. const answer = await callee.createAnswer();
5. await callee.setLocalDescription(answer);
6. await caller.setRemoteDescription(answer);
The recever's currentDirection is updated at step 5 (half-way through the answer). Likely the application would like to know at 3 when the ontrack events fire.

Today the application is forced to piece together from ontrack and other events what the state of the receivers really are. It's confusing having a pc with a set of receivers and not be able to figure out what their state are without wiring up events and listening to history.

We no longer support getRemoteStreams() but it should be possible to do the equivalent, i.e. "get active receivers".

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1920 using your GitHub account
Received on Friday, 29 June 2018 08:26:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:42 UTC