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

Another API issue: addStream has no callbacks

From: Adam Roach <adam@nostrum.com>
Date: Mon, 25 Feb 2013 15:13:41 -0600
Message-ID: <512BD405.7000405@nostrum.com>
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Sometimes it seems like I'm screaming into the void by posting the 
issues we're actually running into implementing this stuff, but here's 
another problem we've uncovered with the currently defined API:

addStream() can plausibly fail, and some of those failures can occur 
asynchronously. Examples of such failures include exhausting encoders of 
the indicated type (e.g., I might have a device with only one hardware 
video encoder).

While we could allow these calls to succeed and then return an error 
when the application attempts to take further action (e.g., createOffer 
or createAnswer), I think delaying such errors until later will surprise 
and befuddle application developers.

For these reasons, I would propose the addition of success and error 
callbacks to addStream.

/a
Received on Monday, 25 February 2013 21:14:05 UTC

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