-
Notifications
You must be signed in to change notification settings - Fork 65
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Version 3 proposal: Store optional member data in a single hash
This has the benefit of not using a separate hash for every single member's data. As is updated in the documentation, you can store more data for a given member by, for example, encoding a Hash in JSON. Not only will this save on Hash-splosion if using member data in a leaderboard, it also means that when deleting a leaderboard, we can also delete ALL of the member data at once. In version 2.x, if using member data, you would have to go through and delete the member data hashes individually. Yikes!
- Loading branch information
David Czarnecki
committed
Sep 16, 2012
1 parent
7110511
commit ddc5bea
Showing
4 changed files
with
52 additions
and
46 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters