Re: Specify the negotiationneeded event

• From: <piranna@gmail.com>
• Date: Fri, 13 Feb 2015 01:56:39 +0100
• To: Roman Shpount <roman@telurix.com>
• Cc: Justin Uberti <juberti@google.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, Cullen Jennings <fluffy@cisco.com>, Martin Thomson <martin.thomson@gmail.com>, public-webrtc <public-webrtc@w3.org>
• Message-ID: <CAKfGGh2P=XTWafX8vabBOpsjD3jxwQCWoQyYM_qcOVdw_mw+jg@mail.gmail.com>

> I wanted to clarify. As far as I know Chrome currently fires two
> negotiationneeded events when removeTrack is immediately followed by
> addTrack. Is this going to change based on this specification and only one
> negotiationneeded event will be fired?

It should fire only one, and in a second iteration/implementation
detail/left for a future specification, being so smart to detect the
inverse operation (addTrack/removeTrack) leading to the same previous
state and don't dispatch it at all since nothing changed.


-- 
"Si quieres viajar alrededor del mundo y ser invitado a hablar en un
monton de sitios diferentes, simplemente escribe un sistema operativo
Unix."
– Linus Tordvals, creador del sistema operativo Linux

Received on Friday, 13 February 2015 00:57:31 UTC