W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: ISSUE-58: XMLHttpRequest.abort() should just reset the object

From: Jim Ley <jim@jibbering.com>
Date: Tue, 11 Apr 2006 10:11:59 +0100
Message-ID: <000a01c65d48$06eea750$2402a8c0@Snufkin>
To: "Web APIs WG \(public\)" <public-webapi@w3.org>

"Jonas Sicking" <jonas@sicking.cc>
>> Why do we need to find a solution for error handling? I thought that 
>> wasn't necessary for "version 1.0".
> Not having error handling at all will seriously cripple the usefulness of 
> the spec.

We've survived so far without error handling other than magic (and 
incomprehensible) status numbers from IE's implementation, and nothing from 
anywhere else.  Errors are rare, and thus virtually nothing you can do as an 
author ("the network's no longer there", erm okay then connect to this site 
and ...)

So I don't think error handling is important, as long as an error doesn't 
look like a valid response and readyState change fires and goes to 4, then 
errors will be generally handled the same as any other malformed response 
coming back from the server.  Dealing with hard network errors is rarely a 
requirement in web-applications, and even if it were possible with XHR, it 
would still not be possible with regular loaded content.

So whilst error is handy, not having it certainly wouldn't cripple the 


Received on Tuesday, 11 April 2006 10:23:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:21 UTC