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

Re: [webrtc-pc] "track" event will fire extra times if applying multiple remote offers

From: stefan hakansson via GitHub <sysbot+gh@w3.org>
Date: Sun, 14 Jan 2018 13:43:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-357512847-1515937403-sysbot+gh@w3.org>
Regarding https://github.com/w3c/webrtc-pc/issues/1729#issuecomment-357493553 I think it is clear from JSEP that multiple remote offers can be applied in sequence (also from the state diagram in sectio 4.3.1). And [[CurrentDirection]] would not be updated until SLD(answer) is done IIUC.

To comment on https://github.com/w3c/webrtc-pc/issues/1729#issue-287276834 : If I read correctly, you'd also get a new track event each time you (from a stable state with a "sednrecv" or "sendonly" transceiver) change direction to "recvonly" / "inactive", followed by associated signaling, and then back to "sendrecv"/"sendonly", createOffer, SLD(offer), send off, and the remote endpoint applies the offer.

Is that what we want?

GitHub Notification of comment by stefhak
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1729#issuecomment-357512847 using your GitHub account
Received on Sunday, 14 January 2018 13:43:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:58 UTC