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

Make Player object useable in multi workers environment #136

Open
Neraste opened this issue Nov 28, 2020 · 1 comment
Open

Make Player object useable in multi workers environment #136

Neraste opened this issue Nov 28, 2020 · 1 comment
Labels
enhancement New feature or request refactor Make things more beautiful inside, but same outside

Comments

@Neraste
Copy link
Member

Neraste commented Nov 28, 2020

Currently the Player is stored in cache, which is great if a single server worker is running. If two are running, 2 players exists concurrently, implying incoherent behavior.

The player object should be agnostic of its storage process, and a Redis backend should be available to handle the multi workers case.

@Neraste Neraste added enhancement New feature or request refactor Make things more beautiful inside, but same outside labels Nov 28, 2020
@Neraste
Copy link
Member Author

Neraste commented Jan 17, 2021

An easy solution would be to use Redis as cache backend. This way there are no adaptations to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request refactor Make things more beautiful inside, but same outside
Projects
None yet
Development

No branches or pull requests

1 participant