From: John Snow <jsnow@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: QMP and the 'id' parameter
Date: Mon, 9 Nov 2020 20:47:45 -0500 [thread overview]
Message-ID: <62700620-5228-f1cc-f0df-751c0d9f1f82@redhat.com> (raw)
The QMP specification states:
> NOTE: Some errors can occur before the Server is able to read the "id"
> member, in these cases the "id" member will not be part of the error
> response, even if provided by the client.
I am assuming this case ONLY occurs for Parse errors:
{'class': 'GenericError', 'desc': 'JSON parse error, expecting value'}
And I am assuming, in the context of a client that /always/ sets an 'id'
for its execute statements, that this means that any error response we
receive without an 'id' field *must* be associated with the
most-recently-sent command.
Correct?
--js
next reply other threads:[~2020-11-10 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 1:47 John Snow [this message]
2020-11-10 6:22 ` QMP and the 'id' parameter Markus Armbruster
2020-11-10 9:15 ` Daniel P. Berrangé
2020-11-10 10:27 ` Markus Armbruster
2020-11-10 16:32 ` John Snow
2020-11-11 8:27 ` Markus Armbruster
2020-11-20 0:22 ` John Snow
2020-11-20 10:25 ` Markus Armbruster
2020-11-20 16:49 ` John Snow
2020-11-23 6:57 ` Markus Armbruster
2020-11-30 18:32 ` John Snow
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=62700620-5228-f1cc-f0df-751c0d9f1f82@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@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).