Re: serialization format

Markus Wanner <[email protected]> writes:

> On 04/07/2016 05:21 PM, Stephen Leake wrote:
>> Peter Stirling <[email protected]> writes:
>>> I apologise for being late to the part here: Is the goal here to
>>> reduce the barrier to entry for automate clients (by using something
>>> which has a decent chance of having a parsing library in most
>>> languages)?
>
> Yes, that'd be one of the nice properties of a standard format; whether
> its a binary (e.g. ASN.1) or textual (e.g. YAML) one.
>
>> But only if the current output is preserved as an option; I've got it
>> working with Emacs. Which is a non-starter; we don't have enough
>> manpower to maintain two output formats.
>
> Well, I'm willing to put some effort into it and I certainly value
> backwards compatibility as well, yes. However, there can only be one
> format that monotone uses internally (think pre vs post flag day). 

There's a version number in the internal format, so we don't need a flag
day (or maybe that was on a branch; anyway, we can add one). We do need
to maintain both formats for compatibility with old databases.

-- 
-- Stephe