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

On Thu, Aug 8, 2013 at 12:05 PM, Nilsson, Claes1
<[email protected]> 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/