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

Implement queued database operations per user/subsystem #3

Open
Olink opened this issue May 4, 2014 · 2 comments
Open

Implement queued database operations per user/subsystem #3

Olink opened this issue May 4, 2014 · 2 comments

Comments

@Olink
Copy link
Owner

Olink commented May 4, 2014

Requirements:

Reason:
Since this game is web based, all requests will be async. We need to be able to ensure proper behavior, should a player open 10 tabs and click the buttons all at once. This demands that each response is blocked on a queue of database operations for that user, such that we do not get some weird bugs where they can buy things for free. It is per user for most operations, but things such as towns and stuff will need to be queued for that specific object.

@hakusaro hakusaro self-assigned this May 4, 2014
@hakusaro
Copy link
Contributor

hakusaro commented May 4, 2014

on it doc

@Olink
Copy link
Owner Author

Olink commented May 4, 2014

Dont assign yourself a task when the requirement isnt complete. Project management 101.

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

No branches or pull requests

2 participants