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

Re: ISSUE-72: should XMLHttpRequest be an EventTarget?

From: Jim Ley <jim@jibbering.com>
Date: Sat, 8 Apr 2006 12:39:34 +0100
Message-ID: <00e701c65b01$1c4b0010$2402a8c0@Snufkin>
To: "Web APIs WG \(public\)" <public-webapi@w3.org>

"Jonas Sicking" <jonas@sicking.cc>
> There are *a lot* of features about XHR that I would like people to use in 
> the end. onreadystatechange would be nice to get people off of entierly 
> for example since having separate onload, onprogress and onerror is a lot 
> easier to use.

I think onprogress is useful and can be added without effecting anything 
else - ie an an author won't change their code for implementations without 
an onprogress, the readyState=4 will still exist where the we're done is 
finished.

onload and onerror though aren't so useful, because all scripts will still 
have to treat the readyState=4 situation, so there's little benefit to 
authors to have them defined here, it would just lead to more duplicated 
code.

>>  2. Better for new implementations.
>
> I can agree to that.

Well, it means new implementations have to implement more stuff, despite the 
fact that authors will be continuing to author to the old format.  I'd like 
to see changes that can't realistically be used deferred to a later 
specification, where the new neater methods are combined with new 
functionality.

Cheers,

Jim. 
Received on Saturday, 8 April 2006 11:40:55 GMT

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