Re: [libvirt] [Qemu-devel] QMP; unsigned 64-bit ints; JSON standards compliance

On Tue, May 14, 2019 at 10:37:55AM +0100, Dr. David Alan Gilbert wrote: > * Daniel P. Berrangé (berrange(a)redhat.com) wrote: > > On Tue, May 14, 2019 at 08:02:49AM +0200, Markus Armbruster wrote: > > > Eric Blake <eblake(a)redhat.com&gt; writes:

> > Unless I'm missing something, this should ensure we don't loose precision, > > can always parse large numbers, and can internally change QEMU precision > > from int8/16/32 upto full int64 without breaking clients. > > But we could be stricter and simpler in string mode: > > - QEMU & clients MUST format integer fields as strings, always > - QEMU & clients MUST parse only strings for integer fields. > > That's (3) above, but also meets your requirements. Yep, given that we don't actually expose the int8/int16/int32/int64 distinction via the QMP introspection data, that would be fine too. Its basically saying we'll never use JSON's number format.