Hi,
I've noticed that when scrolling through grid using remote virtualization, except for the initial call for data (which only happens once), when scrolling down, every time it needs more data it makes two requests with the exact same request, please see my screenshots attached.
The first screenshot shows the information from the initial data loading call; see how it only requests the top 100.
The two other screenshots are after I scrolled down on the grid until the loading animation showed. Then two requests are made and as the screenshots show, the requests are identical - both requesting the top 100 after skipping 100.
These screenshots were taken using Google Chrome (haven't tried in other browsers), and using your demo page as the test page.
We have a web application using remote virtualization and it is happening in our app with our query, which is extremely large but it seemed to be taking even longer than expected to run, which made me find this issue - it actually causes the server to run the query twice. Could someone please look into this asap as we are trying to create a demo-able proof of concept and at the moment, this doubling of an already slow query is not helping us sell our concept.
I've noticed that when scrolling through grid using remote virtualization, except for the initial call for data (which only happens once), when scrolling down, every time it needs more data it makes two requests with the exact same request, please see my screenshots attached.
The first screenshot shows the information from the initial data loading call; see how it only requests the top 100.
The two other screenshots are after I scrolled down on the grid until the loading animation showed. Then two requests are made and as the screenshots show, the requests are identical - both requesting the top 100 after skipping 100.
These screenshots were taken using Google Chrome (haven't tried in other browsers), and using your demo page as the test page.
We have a web application using remote virtualization and it is happening in our app with our query, which is extremely large but it seemed to be taking even longer than expected to run, which made me find this issue - it actually causes the server to run the query twice. Could someone please look into this asap as we are trying to create a demo-able proof of concept and at the moment, this doubling of an already slow query is not helping us sell our concept.
3 Answers, 1 is accepted
0
Hello Chris,
We are aware of the issue other users also shared the same thoughts:
http://www.kendoui.com/forums/ui/grid/grid-with-remote-virtual-scrolling-fires-mutiple-read-requests-when-scrolling-fast.aspx
I am afraid that there is nothing I can suggest you to avoid such behavior at this point.
Kind Regards,
Petur Subev
the Telerik team
We are aware of the issue other users also shared the same thoughts:
http://www.kendoui.com/forums/ui/grid/grid-with-remote-virtual-scrolling-fires-mutiple-read-requests-when-scrolling-fast.aspx
I am afraid that there is nothing I can suggest you to avoid such behavior at this point.
Kind Regards,
Petur Subev
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!
0
Chris
Top achievements
Rank 1
Rank 1
answered on 19 Feb 2014, 12:11 PM
Hi,
I know this is bumping an old thread here, but we are in a position where this feature would once again be useful and were wondering whether there has been any development that resolved this issue yet ?
I know this is bumping an old thread here, but we are in a position where this feature would once again be useful and were wondering whether there has been any development that resolved this issue yet ?
0
Hello Chris,
The behavior discussed below would require much effort and re-writing of both the the Grid and the DataSource implementations to be avoided. Since it occurs in rare situations and on other side it is really a time consuming task, currently it does not meet our time / value limits.
If the community on the official feedback portal find it really inappropriate then the Dev team will re-consider it.
I am sorry for any inconvenience caused and thank you for the understanding.
Kind Regards,
Petur Subev
Telerik
The behavior discussed below would require much effort and re-writing of both the the Grid and the DataSource implementations to be avoided. Since it occurs in rare situations and on other side it is really a time consuming task, currently it does not meet our time / value limits.
If the community on the official feedback portal find it really inappropriate then the Dev team will re-consider it.
I am sorry for any inconvenience caused and thank you for the understanding.
Kind Regards,
Petur Subev
Telerik
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI now!