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, 06 Apr 2006 11:20:53 +0200
Message-ID: <4434DD75.5030004@ilog.fr>
To: Anne van Kesteren <annevk@opera.com>
CC: Jonas Sicking <jonas@sicking.cc>, "Web APIs WG (public)" <public-webapi@w3.org>

Hi,

Anne van Kesteren wrote:
> 
> On Wed, 05 Apr 2006 22:56:28 +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...

As far as I can see, dispatching another event will not permit to 
distinguished between readyState = 4 that means LOADED and readyState = 
4 that means ABORTED...

However I agree changing status to something else than just HTTP code is 
probably not a good idea. That's why I was proposing (for future 
version) yet another way to get that information...

-- 
Christophe
Received on Thursday, 6 April 2006 09:20:09 GMT

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