W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2016

[webrtc-pc] Pull Request: Revise the rules of the negotiation-needed flag for transceivers.

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Thu, 03 Nov 2016 20:03:09 +0000
To: public-webrtc@w3.org
Message-ID: <pull_request.opened-92229461-1478203387-sysbot+gh@w3.org>
taylor-b has just submitted a new pull request for 

== Revise the rules of the negotiation-needed flag for transceivers. 
Addresses issue #803.

Besides just revising the negotiation-needed sections to deal with
transceivers instead of tracks, this commit makes the following
improvements relevant to the negotiation-needed flag:

- Use an internal slot to represent the flag.
- Only update the flag when applying an answer, or modifying the
  PeerConnection in the "stable" signaling state. *Not* when creating 
- Instead of directly firing the negotiationneeded event when applying
  answer, queue a task to check the flag again and then fire it (which
  is how it's normally fired).
- More thoroughly specify the steps for updating the 
  flag, and the criteria for determining if negotiation is needed.
- Reference these steps in every method where the negotiation-needed
  flag may possibly be updated.
- Remove text talking about RtpReceivers allowing the application to
  control the receipt of media, requiring negotiation. There's no 
  on RtpReceiver that does anything but provide information to the

See https://github.com/w3c/webrtc-pc/pull/913
Received on Thursday, 3 November 2016 20:03:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:49 UTC