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

Allow next throw only after every client reported that "STOOOOP" has finished on their side #54

Open
JustMyGithub opened this issue May 6, 2020 · 4 comments
Assignees
Labels
Milestone

Comments

@JustMyGithub
Copy link

No description provided.

@ApolloLV
Copy link
Collaborator

ApolloLV commented May 6, 2020

This might become possible to do when we improve the server-side stream handling in a future version. Right now the server does not know how many javascript clients are connected. So even if the clients told the server they are finished playing, he would not be able to figure out whether that was everyone. For now, we will have to live with the hard-coded cool down period of #37.

@ApolloLV ApolloLV added this to the Version n+1 milestone May 6, 2020
@ApolloLV ApolloLV self-assigned this May 6, 2020
@JustMyGithub
Copy link
Author

How is that possible? Clients are provided with status update (next through etc.), so the server needs to know the number of clients somehow ?!

@ApolloLV
Copy link
Collaborator

ApolloLV commented May 7, 2020

No, the server just has a list of streams and it pours new game states into every one of them. He does not keep track of which username is associated with each stream, or even whether the user behind a stream is registered or not.

@stheid
Copy link
Collaborator

stheid commented May 18, 2020

related to #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants