Skip to content
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

[Feature Request] Retain control after reconnect #72

Open
m1k1o opened this issue Jun 13, 2021 · 0 comments
Open

[Feature Request] Retain control after reconnect #72

m1k1o opened this issue Jun 13, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@m1k1o
Copy link
Owner

m1k1o commented Jun 13, 2021

If reconnect happens while you are controlling, you loose control. Although, there should be some grace period when user disconnects and his control is taken back.

But since our user diappears on server completly on reconnect, and will be created when he joins again, it would be lot of refactoring (after #48 is finished).

It could be done purely on client, simply storing that information and requesting control again. It could happen, that someone "steals" control while another user is experiencing disconnects. But admin can take his control anyway, so it should not be an issue.

@m1k1o m1k1o added the enhancement New feature or request label Jun 13, 2021
@m1k1o m1k1o changed the title Retain control after reconnect [Feature Request] Retain control after reconnect Jul 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant