qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: ANN: QEMU Monitor Protocol git tree
Date: Wed, 23 Sep 2009 20:45:25 +0200	[thread overview]
Message-ID: <4ABA6CC5.6050708@gnu.org> (raw)
In-Reply-To: <20090923183617.GD23822@shareable.org>

On 09/23/2009 08:36 PM, Jamie Lokier wrote:
> Anthony Liguori wrote:
>> The main advantage of not relying on whitespace terminated messages is
>> that it gives us the ability to pretty print the protocol on the wire.
>> For instance, I'd rather read:
>>
>> { "execute": "info",
>>    "id" : "32",
>>    "arguments": ["cpus"]}
>
> I agree.  It's not even expensive.
>
> It's still useful for parsers to easily find the end before parsing.
>
> So declare the JSON terminator to be "}\n" or "}\r\n".  That shouldn't
> occur anywhere inside a pretty printed structure.  The internal
> closing braces are all followed by a comma.

To be picky, you could have dictionaries pretty printed as

   ...
   'key': {
     'key': {
       'key': {}
     }
   }
}

I think it's either no-delimiter or "\n" or "\r\n".

Paolo

  reply	other threads:[~2009-09-23 18:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22  1:44 [Qemu-devel] ANN: QEMU Monitor Protocol git tree Luiz Capitulino
2009-09-23  1:56 ` Anthony Liguori
2009-09-23  9:57   ` Daniel P. Berrange
2009-09-23 10:57     ` Avi Kivity
2009-09-23 13:40       ` [Qemu-devel] " Paolo Bonzini
2009-09-23 14:04         ` Avi Kivity
2009-09-23 15:19           ` Nathan Baum
2009-09-23 15:40             ` Luiz Capitulino
2009-09-23 18:15           ` Anthony Liguori
2009-09-23 18:36             ` Jamie Lokier
2009-09-23 18:45               ` Paolo Bonzini [this message]
2009-09-23 16:01     ` [Qemu-devel] " Markus Armbruster
2009-09-23 16:11       ` Luiz Capitulino
2009-09-23 18:15         ` Jamie Lokier
2009-09-23 18:18       ` Anthony Liguori
2009-09-23 17:08     ` Daniel P. Berrange
2009-09-23 19:07       ` Luiz Capitulino
2009-09-23 14:18   ` Luiz Capitulino
2009-09-23 18:21     ` Anthony Liguori
2009-09-23 10:08 ` Daniel P. Berrange
2009-09-23 14:21   ` Luiz Capitulino
2009-09-23 15:55   ` Markus Armbruster
2009-09-23 22:37 ` Markus Armbruster
2009-09-24 12:31   ` Luiz Capitulino
2009-09-24 12:44     ` Avi Kivity
2009-09-24 13:05       ` Luiz Capitulino
2009-09-24 13:07         ` Avi Kivity
2009-09-24 13:14           ` Luiz Capitulino
2009-11-11  9:59             ` [Qemu-devel] " Michael S. Tsirkin
2009-09-24 13:28     ` [Qemu-devel] " Markus Armbruster
2009-09-24 19:09       ` Luiz Capitulino
2009-11-11 10:03       ` [Qemu-devel] " Michael S. Tsirkin
2009-11-13  8:38         ` Markus Armbruster

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=4ABA6CC5.6050708@gnu.org \
    --to=bonzini@gnu.org \
    --cc=avi@redhat.com \
    --cc=jamie@shareable.org \
    --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).