Despite the COVID-19 outbreak, our team continues operating at full speed. We are always here to support and answer all your questions.

Feel free to reach out by filling this quick form.

Fill the form
Get Free Trial

Improve user experience with custom data source

Answered
qwalker asked on July 6, 2020

Dear team,
When using flexmonster with custom data source api, we have some questions on user experiences:
1, Each time loading data from server, that “Loading” dialog pops up and interrupts user attention even the loading is fast. Is there a way to disable that loading popup, or configure it to only popup if loading takes longer than X seconds?
2, If you collapse a level and re-expand it again, flexmonster loads that part of data from server again. Can flexmonster cache that data locally?
3, Can we let flexmonster prefetch deeper levels of data so when user expand some level the data is already there and can be displayed instantly? And at the same time flexmonster can do further level of prefetching in background.
I hope flexmonster team can consider these suggestions, and I really hope we have solution for question 1.
 
 
 

1 answer

Public
Illia Yatsyshyn Illia Yatsyshyn Flexmonster July 8, 2020

Hello,
 
Thank you for reaching out to us.
 
1. Our team wants to explain that Flexmonster does not provide the possibility to adjust the behavior of the mentioned pop-up windows.
2, 3. We would like to notice that caching on the client-side and prefetching the data in advance goes against the idea of the custom data source API. The main idea of such a data source is the possibility to load only the data that needs to be displayed. It allows operating with larger data sets without limitation exposed by the client’s browser and the hardware.
 
Concerning the cashing, it is possible to cache responses on the server-side. It allows reducing the time needed for the server to respond. In case Flexmonster Data Server is used, we suggest paying attention to the CacheSizeLimit property of the DataStorageOptions object. It allows specifying the maximum number of cached server responses for every index defined in the DataSources property. Detailed information about the reference configuration can be found in our documentation.
 
We hope it helps.
Please let us know in case any other questions arise.
 
Regards,
Illia

Please login or Register to Submit Answer