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

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

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 8 Aug 2013 12:09:12 +0100
Message-ID: <CADnb78jX0T+fHqJopNsgK3y5k3eGDj3RJZ-2OOBJAOk9a+5j7g@mail.gmail.com>
To: "Nilsson, Claes1" <Claes1.Nilsson@sonymobile.com>
Cc: Jonas Sicking <jonas@sicking.cc>, "www-dom@w3.org" <www-dom@w3.org>, "public-sysapps@w3.org" <public-sysapps@w3.org>
On Thu, Aug 8, 2013 at 12:05 PM, Nilsson, Claes1
<Claes1.Nilsson@sonymobile.com> wrote:
> 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.

That seems somewhat unlikely to me, especially at such a low level.
Typically when scripts are written the expectation is that it will
work (and it's tested until it does) and maybe have some handling for
when things fall apart, but certainly not wide and varied failure
scenarios.


-- 
http://annevankesteren.nl/
Received on Thursday, 8 August 2013 11:09:40 UTC

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