requestEnd, when is it fired?

[Bilal]

Hi,

From what I've read, requestEnd fires at the end of the request to signal that the operation is completed.

First, in case the error event of DataSource is fired, will the requestEnd also fire?

Also, in case there are records created and others updated, DataSource will fire two requests to server (batch mode), one for creation and another for updating. requestEnd fires twice in this case? Or just once, after both requests have been updated? 

 

Regards

Bilal

[Kiril Nikolov]

Hello Bilal,

The requestEnd event will be fired when the error event is fired, the thing is that it will be fired for every single dataSource request, just to indicate the request is no longer in process and it is completed either with error or with success.

Regards,
Kiril Nikolov
Telerik

 

 

[Bilal]

Thanks for the reply. Just an inquiry, requestEnd will be fired when error event is fired? Didn't get well that statement.

 

Best regards

Bilal Haidar

 

[Kiril Nikolov]

Hello Bilal,

It will be fired when the error is fired as well. But you can easily test that in your project as well.

Regards,
Kiril Nikolov
Telerik

 

 

[n/a]

My test indicate that requestStart and requestEnd also fire when a grid filter or a sort is executed (even if serverFiltering and serverSorting is set to false)

When these events fire the requestStart or requestEnd event, the resulting parameter object "type" attribute is set to "read", but there is no network action. I can test for an e.response with requestEnd, but there appears to be no way to determine the true nature of the event using requestStart.

This seems to me to be a bug.

[Ivan Danchev]

Hello James,

The requestStart and requestEnd events firing in this scenario is expected and by design. For more details see Konstantin's reply in the following forum thread.

Regards,
Ivan Danchev
Progress Telerik