Specifying Serialization Class

[chandler-barlow]

Just curious what your thoughts would be on adding the ability to change which typeclass is used for serialization of the messages. I have a project where a majority of the types already implement CBOR serialization and I am curious if it's possible/you would be interested in being able to leverage different classes.

[agentm]

Sure, I'm open to discussing how the API could change to accommodate other serialization methods. I chose winery for its pure speed, ease-of-use, and compactness, but other serialization methods could provide compatibility with other RPC methods.

Could you say more about your proposed use case? For example, assuming you are using CBOR for disk serialization, are you against using a different serialization scheme for RPC? What other benefits might CBOR have for your use case?

[lolepezy]

I support this change, in my project objects are seialised with store, so reusing this would be a neat solution, instead of involving winery.