The serialization code doesn't need to be JSON - I think I could write a base interface / implementation that could be any output type (JSON, binary, XML). The serialize / deserialize code could then call these generic methods that don't care what type of data is being saved / loaded.
The serialization code doesn't need to be JSON - I think I could write a base interface / implementation that could be any output type (JSON, binary, XML). The serialize / deserialize code could then call these generic methods that don't care what type of data is being saved / loaded.