In PR #8, @dob commented on the serialization code. We will eventually switch to a custom serialization format as defined by the PPSPP RFC, but for now we're using JSON. This issue tracks the software architecture for handling this in a way that will make it easy to swap back and forth as needed.
I think go-multicodec will allow a peer to support both codecs at once -- decoding based on an incoming header. So we could implement a new codec based on the RFC spec and then add it to the multicodec that the peer supports. I'm not sure, need to think more about this.
In PR #8, @dob commented on the serialization code. We will eventually switch to a custom serialization format as defined by the PPSPP RFC, but for now we're using JSON. This issue tracks the software architecture for handling this in a way that will make it easy to swap back and forth as needed.
I think go-multicodec will allow a peer to support both codecs at once -- decoding based on an incoming header. So we could implement a new codec based on the RFC spec and then add it to the multicodec that the peer supports. I'm not sure, need to think more about this.