W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2008

[xmlhttprequest2] timeout and JSON

From: Anne van Kesteren <annevk@opera.com>
Date: Fri, 05 Sep 2008 09:55:58 +0200
To: "Jonas Sicking" <jonas@sicking.cc>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.ugz0bk2k64w2qv@annevk-t60.oslo.opera.com>

On Fri, 05 Sep 2008 02:36:58 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
> 1. A timeout property like the one on microsofts XDR. I haven't looked
>     into the specifics of XDRs property, but I would think that an
>     'abort' event should fire as well as readystate transitioning to
>     something if the timeout is reached.

What's wrong with using setTimeout?


> 2. A .responseJSON property. This would return the same thing as the
>     following code:
>
>     if (xhr.readyState != 4) {
>       return null;
>     }
>     return JSON.parse(xhr.responseText);
>
>     However there are a few details that can be quibbled about:
>     a) Should a partial result be returned during readystate 3
>     b) If the property is gotten multiple times, should that return the
>        same or a new object every time.

What's wrong with using JSON.parse?


(I'm not necessarily opposed, but I'd like to only add features that are  
necessary.)


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Friday, 5 September 2008 07:56:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:27 GMT