W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2014

Re: Which stream/transport does PC.oniceconnectionstatechange points to?

From: Justin Uberti <juberti@google.com>
Date: Fri, 17 Oct 2014 20:51:45 -0700
Message-ID: <CAOJ7v-3e1msob+QoF=uBAYXgeSuKGzg6CDKnnXxUhLuWAQ2hnw@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
When IceTransport lands in the spec (as part of doohickeys), you'll be able
to interrogate IceTransport.state on the audio and video transports to
determine this.

On Wed, Oct 15, 2014 at 4:36 AM, Iñaki Baz Castillo <ibc@aliax.net> wrote:

> 2014-10-15 13:25 GMT+02:00 Harald Alvestrand <harald@alvestrand.no>:
> > If we ever add transport objects to the spec (not in version 1.0!), we
> > should expect to see events fired related to single connections, but in
> > version 1.0, the RTCIceConnectionState refers to the aggregate state, not
> > the state of individual transports.
>
>
> Yep. I would have not reported this if browsers behave in that way,
> but AFAIR some browser fires
> oniceconnectionstatechange(connected/completed) twice (I will recheck
> it).
>
> BTW, it is sad that I cannot know whether my video stream is connected
> or not. Typically I wait until the "completed" event in order to begin
> displaying the remote video, but it may happen that the remote video
> has already connected but the audio has not, so I must wait until both
> connect.
>
> Well, hope we can manage per-transport events soon :)
>
>
> --
> Iñaki Baz Castillo
> <ibc@aliax.net>
>
>
Received on Saturday, 18 October 2014 03:52:37 UTC

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