You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mean that with JSON we're getting JSON-string as a response from server, and we're sending POST/PUT requests either with JSON payload, or with multipart/form-data payload.
But with CBOR are we getting just a raw Data as a response from a server? And are we sending binary data as payload for POST/PUT requests all the time?
Sorry for dumb questions, I did some research, but I have no experience with CBOR yet, so idk how binary data exchanging works in comparison with classic json.
Answering your question:
Custom encoders/decoders are not supported at the moment, I mean that everything happens under the hood without ability to set your own encoder/decoder. But I can change it by adding something like CustomDecoder and CustomPayload protocols.
I have a server that supports CBOR and MessagePack, how would I be able to customize the encoder for the payloads and response types?
The text was updated successfully, but these errors were encountered: