[Laszlo-dev] support for the "queuerequests" option for datasets
André Bargull
andre.bargull at udo.edu
Wed Dec 10 11:06:27 PST 2008
Last time when I asked about "queuerequests", you gave me this answer ;-)
On 10/15/2007 6:29 PM, Henry Minsky wrote:
> There is also an old flag on dataset which has been around for a long time,
> called dataset.queuerequests, which is slightly different from
> dataset.multirequest. If true, it says not only to support multiple
> requests, but to try to serialize the responses so that ondata
> events from returning requests are sent in the same order that the
> requests were issued. This behavior is currently only implemented in
> the SWF runtime.
> I don't think this has worked this way for many releases, [...]
>
Maybe 4.0.3? So before the big dataprovider/-request change..
> I wanted to have a little discussion about this bug,
> http://www.openlaszlo.org/jira/browse/LPP-5144, about the
> 'queuerequests' feature of LzDataset.
>
> There has long been an LzDataset option called "queuerequests" in the
> SWF runtime, and I am not certain
> what behavior it is supposed to control.
>
> If you make two successive calls to dataset.doRequest(), and
> queuerequests == true, is that supposed to guarantee
> that the second request does not issue until the "ondata" event of the
> previous request has been received?
>
> I don't think this has worked this way for many releases, and I am
> wondering if we want to support this, or if
> this kind of logic should be handled by the app developer in their application.
>
> Note: There is already another option which was introduced more
> recently, "multirequest", which behaves as follows:
>
> + If yourdataset.multirequest == true, causes successive calls to
> doRequest() to have their own
> internal data loader and data request state. This means that all calls
> will be made, but the order in which the server sees
> them is not guaranteed.
>
> + if yourdataset.multirequest == false, the same loader and
> datarequest object are used, potentially overriding or aborting the
> previous request if it has not completed.
>
>
More information about the Laszlo-dev
mailing list