- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Fri, 22 May 2015 14:56:41 +0000
- To: Peter Thatcher <pthatcher@google.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 22/05/15 16:15, Peter Thatcher wrote: [...] > > * Detection/reporting of that negotiation would be needed: as said > above, there seem to be consensus of that if the new track (provided by > replaceTrack) would require a re-negotiation, replaceTrack should fail. > How quickly can this be detected? How should it be reported back to the > application? > > > I don't recall of the top of my head any situation in which > replaceTrack could trigger a renegotiation. Perhaps if we had some > scenarios were we thought that might come up, we could know how long it > would take to detect. Does anyone have any concrete examples? I agree, some concrete examples here would be helpful.
Received on Friday, 22 May 2015 14:57:08 UTC