W3C home > Mailing lists > Public > public-media-capture@w3.org > January 2014

Re: MediaError object (Re: New Editor's draft v20131225)

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 9 Jan 2014 12:18:40 +1100
Message-ID: <CAHp8n2mLAT7zB-RnH1BaYVDaqBk1-t3ueOzgiJwghu6pBGGt5A@mail.gmail.com>
To: Jan-Ivar Bruaroey <jib@mozilla.com>
Cc: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On Thu, Jan 9, 2014 at 9:33 AM, Jan-Ivar Bruaroey <jib@mozilla.com> wrote:
> On 1/8/14 4:57 PM, Harald Alvestrand wrote:
>
> On 01/08/2014 10:31 PM, Jan-Ivar Bruaroey wrote:
>
> On 1/8/14 1:27 PM, Harald Alvestrand wrote:
>
> The constraintName property (and the sdpLineNumber property in the WebRTC
> draft) were added for reasons that seemed good at the time; you can't
> indicate a line number with an error code.
>
>
> But you can in a message-field, which I understand DOMError will grow. Why
> is that not sufficient?
>
> Because that means you can only get it out via parsing the text of the
> field, which means that the format of the text message is part of your API,
> cannot be allowed to vary between implementations, and has to be specified
> in your specifications.
>
>
> You're missing my question. Who needs SDP line numbers other than for
> debugging? What software needs this information?

If I was told which line of SDP produced problems, then I can change
that line programmatically and fix up a broken connection attempt. Why
would that not be desirable?

Silvia.
Received on Thursday, 9 January 2014 01:19:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:23 UTC