W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2016

Dropping SDP-specific errors

From: Dominique Hazael-Massieux <dom@w3.org>
Date: Thu, 28 Jan 2016 15:31:27 +0100
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <56AA263F.3070901@w3.org>
Hi,

The spec has had for ever a description of an RTCSdpError interface:
http://w3c.github.io/webrtc-pc/#rtcsdperror

The intent of that error (when it was added in 2012) was to have the 
ability to report in a specific attribute the line number at which a 
potential error in the SDP blob had been detected by the browser when 
trying to apply it with setLocalDescription and setRemoteDescription.

While that error has been defined, it was never referenced from anywhere 
in the spec (in particular, not from setLD nor setRD), and as far as I 
can tell, is not provided by any browser.

 From what I understand, their lack of availability hasn't been high on 
anyone's complaint lists, and it is in general dubious what one could do 
programmatically once provided with the SDP line number.

We also know based on our experience in getUserMedia that defining 
errors with special attributes is non trivial to specify, and I 
understand from some implementors that they're not trivial to integrate.

I have thus taken the approach of getting rid of RTCSdpError in my pull 
requests that overhaul the error management of the spec
   https://github.com/w3c/webrtc-pc/pull/468
   https://github.com/w3c/webrtc-pc/pull/472 in particular 
https://github.com/w3c/webrtc-pc/commit/154ea0b6cb5d475cdd591a92212f518484b1d853

I'm seeking feedback on whether that's an acceptable approach.

Dom
Received on Thursday, 28 January 2016 14:31:32 UTC

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