DBSC performs well during active use of the web app but struggles when the device or web app has been idle for a while.
If the device has been unused or a browser tab inactive, the auth cookies will expire. Before allowing workload requests, the cookie needs to be updated. This requires the client to wait for a network call to the session refresh endpoint before workload navigation can proceed. Therefore, there are two requests:
Session refresh request.
Wait for response.
Workload request.
We can address this problem by including a special header in the request with refresh session information. There could be alternative approaches.
DBSC performs well during active use of the web app but struggles when the device or web app has been idle for a while.
If the device has been unused or a browser tab inactive, the auth cookies will expire. Before allowing workload requests, the cookie needs to be updated. This requires the client to wait for a network call to the session refresh endpoint before workload navigation can proceed. Therefore, there are two requests:
We can address this problem by including a special header in the request with refresh session information. There could be alternative approaches.
Similar issue discussed here: https://github.com/WICG/dbsc/issues/12