[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: A brief look at deprecating our JSON extensions over RFC 8259
From: |
Peter Krempa |
Subject: |
Re: A brief look at deprecating our JSON extensions over RFC 8259 |
Date: |
Mon, 22 Feb 2021 19:25:49 +0100 |
User-agent: |
Mutt/1.14.6 (2020-07-11) |
On Mon, Feb 22, 2021 at 19:22:49 +0100, Peter Krempa wrote:
> On Mon, Feb 22, 2021 at 18:42:00 +0100, Paolo Bonzini wrote:
> > On 22/02/21 15:57, Markus Armbruster wrote:
> > > * The block layer's pseudo-protocol "json:" (which can get embedded in
> > > image headers)
> >
> > If it gets embedded in image headers, I don't think we'll be able to
> > deprecate it ever. We'd need to keep a converter for old images, at which
> > point it's simpler to keep the extensions.
>
> The converter or better 'fixer' actually doesn't need to be able to
> interpret the old string, just accept a new. IOW it's more of a
> documentation problem, because qemu-img can already do that since it's
> able to write invalid JSON without interpreting it:
[...]
I forgot to add that such strings would be user-originated in the first
place. The qemu-generated one are (presumably) correct JSON.