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: Thu, 13 Apr 2006 10:32:55 +0100
Message-ID: <00f501c65edd$3e965220$2402a8c0@Snufkin>
To: "Web APIs WG \(public\)" <public-webapi@w3.org>

"Christophe Jolif" <cjolif@ilog.fr>
> Even though you can always imagine to find solution to workaround it. I 
> think it is a bad idea to go to 4 without having a clear knowledge of what 
> the status really is (successful or erroneous). Indeed bad or null XML can 
> be due to a bug on the server, not necessarily a network error!

Currently I don't think we can avoid it, there's a lot of content that 
assumes there will always be a 4, and use it to enable/disable controls 
whilst the request is being made.  If we make 4 optional then this content 
will break.


Received on Thursday, 13 April 2006 09:34:13 UTC

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