W3C home > Mailing lists > Public > public-sysapps@w3.org > August 2013

RE: [DOMError]: Subclassing DOMError to increase granularity of error handling?

From: Nilsson, Claes1 <Claes1.Nilsson@sonymobile.com>
Date: Thu, 8 Aug 2013 13:05:07 +0200
To: 'Anne van Kesteren' <annevk@annevk.nl>
CC: Jonas Sicking <jonas@sicking.cc>, "www-dom@w3.org" <www-dom@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>
Message-ID: <6DFA1B20D858A14488A66D6EEDF26AA301A33878B42A@seldmbx03.corpusers.net>
This is not just for debugging. Looking at the example I give in the mail, i.e. when the attempt to create a TCP socket fails I expect the web application to handle each error situation ("no network contact","peer does not respond", "local address/port pair is already in use") differently.

Claes



> -----Original Message-----
> From: annevankesteren@gmail.com [mailto:annevankesteren@gmail.com] On
> Behalf Of Anne van Kesteren
> Sent: den 8 augusti 2013 12:56
> To: Nilsson, Claes1
> Cc: Jonas Sicking; www-dom@w3.org; public-sysapps@w3.org
> Subject: Re: [DOMError]: Subclassing DOMError to increase granularity
> of error handling?
> 
> On Thu, Aug 8, 2013 at 11:47 AM, Nilsson, Claes1
> <Claes1.Nilsson@sonymobile.com> wrote:
> > Sorry, I don't follow. I thought I explained the issue earlier in
> this thread. See http://lists.w3.org/Archives/Public/public-

> sysapps/2013Aug/0004.html.
> 
> That message does not make it clear why the granularity is desired at
> the application layer. E.g. do you expect these to be used mostly for
> debugging or do you expect the implementation to do different things
> depending on the error it gets? If it's the former having whatever
> error name is fine as long as the message is detailed and debugging
> tools are good. If it's the latter we might need something else.
> 
> 
> --
> http://annevankesteren.nl/

Received on Thursday, 8 August 2013 11:05:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:36:14 UTC