- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Sat, 2 Mar 2013 21:51:42 +0000
- To: Eric Rescorla <ekr@rtfm.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
We need a similar set of error events for recording. It would be good to find a way to do this without creating a lot of new classes. Could we define a single that gUM, webRTC, recording and takePhoto could use? Jim On Mar 2, 2013, at 9:17 AM, "Eric Rescorla" <ekr@rtfm.com> wrote: > Hi folks, > > I'm starting to come to the conclusion that we need some ways > to implement error notification as distinct from either setLocal/setRemote > or state notification. Here are some examples of events that don't > seem to me to have a logical way to report to the programmer: > > - ICE allocation failed (e.g., couldn't actually allocate sockets for > each component.) Obviously, you could report that allocation > is *done* but it's not like a naive application is going to notice > that candidates are missing. > > - DTLS-SRTP handshake failed. > > - The ever-famous "internal error". > > I would suggest that we have some sort of "onerror" event, perhaps > with a numeric error enum and a string that is explanatory. > > Thoughts, > -Ekr > > >
Received on Saturday, 2 March 2013 21:52:08 UTC