Re: serialization format

Markus Wanner <[email protected]> Wed, 6 Apr 2016 07:28:39 +0200
Newsgroups gmane.comp.version-control.monotone.devel
Message-ID <[email protected]>
On 04/06/2016 05:26 AM, J Decker wrote:
> If the structures might mutate with time something like json is pretty brief.
> if you have high reliability, sqlite for instance will store a blob
> with only \0 for the 0  and \\ for \ ...

JSON doesn't handle binary welll, it's a text format. Usually, base64 is
used for binary data inside JSON - which is neither human readable nor
space efficient.

> which results in a copy or shift of data but only a simple comparison
> if '\\'   kinda like base 254 sorta :)
> depending on what character happens least you could replace <nul> for
> <del> or something ...

That's nonsense, according to http://stackoverflow.com/a/1443240, the
JSON spec supports only 94 Unicode characters that can be represented as
one byte (in UTF-8).

Nor is there any canonical *and* human readable variant.

If human readable, I'd currently prefer to try something canonical
that's still valid YAML.

Kind Regards

Markus Wanner