-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection improvements #53
Comments
@abustany please confirm if it fits to what we discussed. FE generates a new SessionID on App loading. It represents a distinct journey of the user on the App. It sends it as parameter in the initial and subsequent
The intent is for the FE to be able to confirm if it is still in sync with the BE after a connection interruption. |
Reformulated:
When the SSE connection is interrupted (e.g. because the user switched tab, or networking issues).
Then the BE ends up dropping the session after a while. If the FE doesn't notice it, it could show the user wrong information.
For example, the FE shows the Room, but updates aren't received.
As long as the SSE connection is not doing errors, the session cannot have been lost.
But on error: It could be because of networking error. In this case, the session has not been lost: Only the SSE must be reopen.
Or it could be that the session has been Lost.
But the SSE api doesn't seem to allow knowing that. Thus, we must find a way for the FE to ask the BE if the session is still there.
Original:
The text was updated successfully, but these errors were encountered: