To improve performance and address various issues, changes have been made to how our LO app manages users in cache and the configured threshold time.
In the new version 1.6.5, a significant change has been implemented. Previously, in older versions, the expiration time for user access was continuously extended with each request, resetting the inactivity period (threshold) whenever the user became active again.
Starting from version 1.6.5, users will have access and treated as active until the end of the configured threshold period. However, after the treshold time, LO will not extend the expiration time and users will treated as inactive users immediately and their seats can be freed up for others. These users will not lost their access after the static treshold period, they will be only treated as inactive, and they can regain a new active period if a subsequent request is made.
Example
Threshold: 1 hour (60 minutes).
Before version 1.6.5:
First request/activity: User has access from 10:00 to 11:00.
Second request/activity: User becomes active at 10:05, and the expiration time is updated to 11:05.
Third request/activity: User becomes active at 10:10, and access is extended until 11:10.
After version 1.6.5:
First request/activity: User has access from 10:00 to 11:00.
Second request/activity: User becomes active at 10:05, and the expiration time remains at 11:00.
Third request/activity: User becomes active at 10:10, and the expiration time remains at 11:00.
After 11:00, the user will receive a notification indicating that their access has been revoked and needs to be renewed.
If there are empty seats at 11:00 or 11:01, the user will regain access.
If there are no empty seats, the user will need to wait until a seat becomes available if someone else has been granted access ahead of them.