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

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.


> -----Original Message-----
> From: [] On
> Behalf Of Anne van Kesteren
> Sent: den 8 augusti 2013 12:56
> To: Nilsson, Claes1
> Cc: Jonas Sicking;;
> Subject: Re: [DOMError]: Subclassing DOMError to increase granularity
> of error handling?
> On Thu, Aug 8, 2013 at 11:47 AM, Nilsson, Claes1
> <> wrote:
> > Sorry, I don't follow. I thought I explained the issue earlier in
> this thread. See

> 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.
> --

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