I implemented it exactly as Daniel described in the rewrite and I do believe
it's the most logical thing to do.
2010/1/17 Daniel Friesen
> Isn't that a loose use of the term "success" originating in confusion
> caused by abstraction?
>
> We call it "success" because that's it's a word describing
Isn't that a loose use of the term "success" originating in confusion
caused by abstraction?
We call it "success" because that's it's a word describing what we
expect it to do. The browser's actual xhr has no concept of "success" on
it's own, that is determined by the library/application based
It's not really clear what it should call - maybe it should only call
the complete request and neither the error or success. When I looked
into it recently some browsers called success and some called nothing
(Opera). I normalized it to success across the board but I'm open to
further debate.
--Jo
