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

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

From: Christophe Jolif <cjolif@ilog.fr>
Date: Thu, 13 Apr 2006 14:41:59 +0200
Message-ID: <443E4717.2010102@ilog.fr>
To: Jim Ley <jim@jibbering.com>
CC: "Web APIs WG (public)" <public-webapi@w3.org>

Jim Ley wrote:
> "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.

Yes, I'm unfortunately aware of that  ;) That's why the only solution is 
to have an additional error handling stuff to detect erroneous cases... 
(maybe only in next version).

Received on Thursday, 13 April 2006 12:40:57 UTC

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