You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2022. It is now read-only.
When a user sends a synchronization request with a unknown peerID, the synchronization crashes and all other connected users receive a raw synchronization request.
If a peer sends a message to broadcast but is still unknown to the
server, his message is simply ignored.
Before the first synchronization, a peer cannot send his position but
I'd say it is safer this way anyway and is not much of a problem.
In any way, the server should not throw any exception in this case.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a user sends a synchronization request with a unknown peerID, the synchronization crashes and all other connected users receive a raw synchronization request.
Server exception:
The text was updated successfully, but these errors were encountered: