- From: Sunava Dutta <sunavad@windows.microsoft.com>
- Date: Fri, 19 Sep 2008 19:22:22 -0700
- To: Jonas Sicking <jonas@sicking.cc>
- CC: Anne van Kesteren <annevk@opera.com>, WebApps WG <public-webapps@w3.org>, Gideon Cohn <gidco@windows.microsoft.com>, Zhenbin Xu <Zhenbin.Xu@microsoft.com>, IE8 Core AJAX SWAT Team <ieajax@microsoft.com>
Thanks Jonas. I realize XHR2 is not a priority compared on XHR1. Nonetheless, the later it gets the less likelihood of making small tweaks in the timeout for IE8. In that case we can still have the discussion at the groups convenience and I'll revisit the issue of complying to the eventual publicly standardized spec on this for the next release of IE. > -----Original Message----- > From: Jonas Sicking [mailto:jonas@sicking.cc] > Sent: Thursday, September 18, 2008 8:31 AM > To: Sunava Dutta > Cc: Anne van Kesteren; WebApps WG; Gideon Cohn; Zhenbin Xu; IE8 Core > AJAX SWAT Team > Subject: Re: [xmlhttprequest2] timeout and JSON > > On Wed, Sep 17, 2008 at 3:03 AM, Sunava Dutta > <sunavad@windows.microsoft.com> wrote: > > Jonas said > >> I guess IE doesn't have an abort event on the XHR object (is this > >> correct?) so the relation between ontimeout and onabort is undefined > as > >> far as the IE implementation goes. > > > > Correct. We do have abort and timeout, and adding onabort in the > future IE release will have to be considered so we should define the > relationship. As you mentioned, a possible good definition of timeouts > is that a 'timeout' event should fire (which will trigger ontimeout) > and then abort() should be called which will result in an 'abort' even > (which will trigger onabort). > > Sounds good to me. Would be great to hear what other people think on > having timeout in general and the specifics regarding what should > happen when the timeout fires. > > / Jonas
Received on Saturday, 20 September 2008 02:23:08 UTC