Change server save state implementation to only send deltas #34
Description
From a comment in #33:
Future plans include only POSTing the deltas of state changes. Right now, if you're editing a 40MB model, each edit ends up sending 40MB to the server. This is obviously not efficient. By only sending changes to the save state, and letting the server do the rest of the work to generate a whole savestate, then only the first save attempt will require 40MB. Thereafter, any changes will probably be measured in kilobytes.