-
Bug
-
Resolution: Done
-
Minor
-
4.0.2
-
-
MOODLE_400_STABLE
-
MOODLE_401_STABLE
-
Moodle App 4.1.0
For example, when a moderator starts a meeting, or when a user enters a meeting that is already ongoing, it takes a while for the app to know that the meeting started or the user joined. This is because the get_meeting_info WS uses a cache to improve performance.
The WS supports a parameter updatecache to force updating the cached data, but Laurent warned that we shouldn't abuse it because it can affect the server.
IMO we should force updating the cache after a user joins a meeting, so the app displays the new data.
We should decide if we also want to use it when the user performs a PTR, because right now the PTR will always get cached data so it can display outdated info.
Related issue: