More permanent storage for game states

[cpjolicoeur]

To make game saving/reloading easier and more reliable and to keep the memory footprint of the process down, we should probably store and load the game states from redis or something similar. Games that have been completed can probably be archived in something like a sqlite (or any kind) of database, but moving game saves outside of the local processes memory will allow for better persistence and memory usage.

If agreed, I can probably tackle this

[mrroach]

Yup, that sounds good. My lazy thought has been to just pickle the game
objects, but extra credit for a real serialization format ;-)
On Feb 4, 2014 6:16 AM, "Craig P Jolicoeur" notifications@github.com
wrote:

To make game saving/reloading easier and more reliable and to keep the
memory footprint of the process down, we should probably store and load the
game states from redis or something similar. Games that have been completed
can probably be archived in something like a sqlite (or any kind) of
database, but moving game saves outside of the local processes memory will
allow for better persistence and memory usage.

If agreed, I can probably tackle this

Reply to this email directly or view it on GitHubhttps://github.com//issues/11
.

[cpjolicoeur]

Yeah, I started on it this morning and was just going to cPickle them directly. Might just try to get that going before writing some kind of nicer/slicker custom serializer for now.

[mrroach]

SGTM

On Tue, Feb 4, 2014 at 8:28 AM, Craig P Jolicoeur
notifications@github.comwrote:

Yeah, I started on it this morning and was just going to cPickle them
directly. Might just try to get that going before writing some kind of
nicer/slicker custom serializer for now.

Reply to this email directly or view it on GitHubhttps://github.com//issues/11#issuecomment-34077598
.