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

[webrtc-pc] How local peer learns of transceiver.stop() on remote peer

From: aboba via GitHub <sysbot+gh@w3.org>
Date: Wed, 11 May 2016 22:01:21 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-154353058-1463004080-sysbot+gh@w3.org>
aboba has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== How local peer learns of transceiver.stop() on remote peer ==
What event occurs on the remote peer when transceiver.stop() is called
 on the local peer? Presumably the negotiation-needed flag is set on 
the local peer, there is an O/A exchange and somehow the application 
on the remote peer finds out that the transceiver has been stopped.

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/632 using your GitHub account
Received on Wednesday, 11 May 2016 22:01:23 UTC

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