From: Peter Dimov (pdimov_at_[hidden])
Date: 2020-09-16 14:26:00
Vinnie Falco wrote:
> If I make a library that has a public function which accepts a parameter
> of type json::value, I don't expect to see binary objects in it nor would
> I want to have to write code to handle something that is not part of JSON.
> And I expect that things round-trip correctly, i.e. if I serialize a
> json::value and then parse it, I get back the same result. This is clearly
> impossible if the json::value contains a "binary" string.
"Binary string" is basically JSON string with UTF-8 validation turned off;
it's a common thing to want to send/receive and the binary formats are
arguably correct in offering it as a specific type. Of course this doesn't
change the fact that it's not representable in standard JSON.