W3C home > Mailing lists > Public > public-ortc@w3.org > September 2016

[ortc] Sender.setTransport a promise due to async issues?

From: Robin Raymond via GitHub <sysbot+gh@w3.org>
Date: Fri, 09 Sep 2016 23:42:09 +0000
To: public-ortc@w3.org
Message-ID: <issues.opened-176137934-1473464527-sysbot+gh@w3.org>
robin-raymond has just created a new issue for 

== Sender.setTransport a promise due to async issues? ==

It's possible that the transport passed into `sender.setTransport` 
dies just moments before the `setTransport` is called unknown to the 
app developer (e.g. DTLS asynchronously failed to negotiate). Thus the
 `setTransport` would throw an exception because the passed in 
`transport` is dead. The programmer would NOT have received the 
`transport` state change and thus would be unaware anything went wrong
 in advance and could not substitute an alternative transport before 
the promise is fulfilled upon receiving the state change event (and 
thus disregard any setTransport exceptions due to failed states that 
are not relevant).

Please view or discuss this issue at 
https://github.com/w3c/ortc/issues/598 using your GitHub account
Received on Friday, 9 September 2016 23:42:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 9 September 2016 23:42:16 UTC