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

Re: XMLHttpRequest (re)synchronization

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 19 Sep 2006 10:55:21 -0000
To: "Robin Pelgrim" <robinpelgrim@zonnet.nl>
Cc: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.tf4a4ehn64w2qv@id-c0020.emi.ac.ma>

On Sat, 01 Jul 2006 22:32:54 -0000, Robin Pelgrim <robinpelgrim@zonnet.nl>  
wrote:
> Please watch closer to the functionality of XMLHttpRequest.
> Since it used mostly in a Javascript environment, where no threading  
> functions are supported (at the moment) ,
> ways for (re)synchronize asynchronous requests are insufficiant.
> Since there is no Thread.sleep functionality in Javascript there is no  
> way wait for the request to be finished without leaving a function  
> (without using setTimeout).
> This is unacceptable for application building. It's al so clumsy,  
> primitive.
> I expect more from W3C and introduce good standards.
> Till there is no Threading functionality in JavaScript, the  
> XMLHttpRequest object should be extended with
> a 'resync' function. With this function you (simply) can wait for a  
> async request to finish.
>
> (Of coarse it would be better to impement Threading functionality in JS,  
> but for the moment it just isn't there).
>
>
> it's far from complete by now, please try to improve the standards.

I don't really get this comment. Why is it clumsy, insufficient and  
primitive?


It's also unclear why you can't use a synchronize request which is  
functionality the API provides.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 19 September 2006 10:56:07 GMT

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