qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] RFC: libyajl for JSON
Date: Tue, 3 Nov 2015 06:40:32 -0700	[thread overview]
Message-ID: <5638B950.5030009@redhat.com> (raw)
In-Reply-To: <20151103081917.1d348ad1@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1894 bytes --]

On 11/03/2015 06:19 AM, Luiz Capitulino wrote:
> On Tue, 03 Nov 2015 08:17:58 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
> 
>>> So at this point, I want to see if lloyd makes any progress towards an
>>> actual yajl release and/or adding a co-maintainer, before even trying to
>>> get formal upstream support for single quoting.  We could always create
>>> a git submodule with our own choice of fork (since there are already
>>> forks that do single-quote parsing) - but the mantra of 'upstream first'
>>> has a lot of merit (I'm reluctant to fork without good reason).
>>
>> The value proposition of replacing our flawed JSON parser isn't in
>> saving big on maintenance, it's in not having to find and fix its flaws.
>>
>> If the replacement needs a lot of work to fit our needs, the value
>> proposition becomes negative.
>>
>> A JSON parser shouldn't require much maintenance, as JSON is simple,
>> doesn't change, and parsing has few system dependencies.
> 
> Let me suggest this crazy idea: have you guys considered breaking
> compatibility?

As in, requiring QMP clients to send "quotes" rather than 'quotes'?
It's worth considering (we already guarantee that our output is strict
JSON, and that the 'quotes' on input is merely for convenience).  If we
want to go that route, than 2.5 should document loudly that we are
deprecating 'quotes' in QMP, so that 2.6 can actually remove it when
switching to yajl.  And as single quotes appears to be the only JSON
extension we have been relying on, I think that would indeed free us
from having to wait for a yajl release or carry our own yajl fork.

Interesting idea; I'm still thinking whether it would help us more than
it would hurt lazy clients that were depending on the extension.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2015-11-03 13:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 19:45 [Qemu-devel] RFC: libyajl for JSON Eric Blake
2015-10-30 20:16 ` Peter Maydell
2015-11-02  8:40 ` Markus Armbruster
2015-11-02 11:49   ` Paolo Bonzini
2015-11-02 12:56     ` Markus Armbruster
2015-11-02 13:47       ` Paolo Bonzini
2015-11-02 14:10   ` Stefan Hajnoczi
2015-11-02 15:46   ` Eric Blake
2015-11-02 19:10     ` Markus Armbruster
2015-11-02 20:08       ` Eric Blake
2015-11-03  7:17         ` Markus Armbruster
2015-11-03 13:19           ` Luiz Capitulino
2015-11-03 13:38             ` Paolo Bonzini
2015-11-03 13:46               ` Luiz Capitulino
2015-11-03 13:53                 ` Paolo Bonzini
2015-11-03 14:26                   ` Luiz Capitulino
2015-11-03 14:53                     ` Paolo Bonzini
2015-11-03 15:08                     ` Markus Armbruster
2015-11-03 13:40             ` Eric Blake [this message]
2015-11-03 13:44               ` Daniel P. Berrange
2015-11-03 13:53               ` Luiz Capitulino
2015-11-02 13:17 ` Luiz Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5638B950.5030009@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).