W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2015

Re: Specify the negotiationneeded event

From: Justin Uberti <juberti@google.com>
Date: Tue, 17 Feb 2015 16:46:14 -0800
Message-ID: <CAOJ7v-03dh6n3i4QE9Ku_h0pbzK7j8fueOhDEaz+62CZO0Czww@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>, Adam Bergkvist <adam.bergkvist@ericsson.com>, Cullen Jennings <fluffy@cisco.com>, public-webrtc <public-webrtc@w3.org>
On Tue, Feb 17, 2015 at 2:27 PM, Martin Thomson <martin.thomson@gmail.com>

> On 18 February 2015 at 05:34, Justin Uberti <juberti@google.com> wrote:
> >> Can't we spec this in a way that allows implementations capable of
> >> detecting that a potential onNN will be cancelled before signaling state
> >> becomes stable to suppress that onNN?
> >
> >
> > I am sure that we could, but I think we need to consider whether there is
> > any real-world benefit. The actions mentioned in this thread (e.g.
> adding a
> > track and then removing it immediately) seem like academic cases.
> Yes, I wouldn't bother with that.  What concerns me more is what Roman
> pointed out: some applications rely on getting multiple events
> (obviously they aren't using Firefox...), and even as described, the
> event will fire less than they might previously have relied on.
> I'm not super-concerned about that.  Applications that blindly
> renegotiate based on the event aren't going to work particularly well
> anyway.  Justin's proposed formulation does address that by ensuring
> that dirty (what I think we should call negotiationNeeded) is only
> cleared if the session description completely covers the requested set
> of channels/tracks.

Agree with this, as well as your suggested naming.
Received on Wednesday, 18 February 2015 00:47:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:04 UTC