We have almost 15,000 events for MSFS2020 and the list for Xplane is growing.
I can understand that this many events to transfer can take some time.
I also think we should take measures to minimize the amount of data that needs to be transferred.
Here are some ideas:
Separate update operation for MSFS2020 and Xplane. If I have selected MSFS2020, I don't need to get updates for Xplane. If I select Xplane, then I stop getting MSFS2020 updates and only get Xplane updates. It seems both databases are being sent with every refresh.
Implement a time stamp for the last database change that can be used to signal to the user whether his local database is outdated or not. It seems the Updates occur whenever the refresh button is pressed regardless of whether there are new events or not.
Implement only one mandatory local database update per day. Any other update within this period, only by user request. That would require an "update local database button" in the main list page.
Eliminate the waiting time after an event is added or modified. It is very annoying to have to wait 5 to 10 seconds for the web to return control, to then wait another 5 seconds for the "successful" message to go away, and not be able to do anything. Find a way to display the "Event added successfully" message without blocking the operation of the page.
Currently I notice the first page load of the day reloads the database, then checks user credentials, but then it does what appears to be a reset after that. Can't that last operation be eliminated or integrated with the first load of the page?
We have almost 15,000 events for MSFS2020 and the list for Xplane is growing. I can understand that this many events to transfer can take some time. I also think we should take measures to minimize the amount of data that needs to be transferred. Here are some ideas: