That's right - there shoudl be no need for this service in DHTML. We
shouldn't need to help the browser manage the request queue like we do
in Flash.
While this test confirms that multiple outstanding XHR requests will get
handled properly by the browser, it doesn't really test dataset queuing.
Remember, datasets have the queuerequests attribute which determines
what happens when a doRequest() call is made while another request is
already in progress. If queuerequests==true, the dataset should build
up a queue of requests and fire them off sequentially after previous
requests return.
This is something we need to test in DHTML.
So if queuerequests is not asserted, does that mean we would actually want
to abort an outstanding request? XMLHTTPRequest has some kind of abort
feature but I have not tried it.
_______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
