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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 07 Apr 2006 00:32:35 -0700
Message-ID: <44361593.10303@sicking.cc>
To: Anne van Kesteren <annevk@opera.com>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>

Anne van Kesteren wrote:
> 
> On Thu, 06 Apr 2006 11:28:09 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
> 
>>>> If that is indeed true we need to fix it I agree. Is there a 
>>>> sensible  value we could set .status to for example?
>>>
>>>
>>> Lets keep .status an HTTP status code. What about dispatching an 
>>> abort  event on the object as I suggested? Not sure if that's 
>>> appropriate for  this version though...
>>
>>
>> We have already talked about setting .status to -1 in some error  
>> conditions. Aborting is arguably an error condition.
> 
> I don't like that idea. I believe we also opted not to do it given that  
> people might depend on the way .status acts now in certain error  
> conditions. It also makes the attribute unnecessary complex.

I don't think we have addressed error handling yet, so we should just 
include this case when we decide that.

/ Jonas
Received on Friday, 7 April 2006 07:32:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT