All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: amit.shah@redhat.com, david@gibson.dropbear.id.au,
	qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] More structured migration URIs?
Date: Mon, 05 Jan 2015 10:02:39 -0700	[thread overview]
Message-ID: <54AAC3AF.4050302@redhat.com> (raw)
In-Reply-To: <20150105124559.GM29381@redhat.com>

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

On 01/05/2015 05:45 AM, Daniel P. Berrange wrote:

>> It all gets a bit more complicated when an application could specify
>> an arbitrary exec: uri through that API, rather than you knowing what it's
>> doing.
> 
> True, the QMP command would need to support a union of different options
> switched depending on the protocol type. Not sure if QMP can do that or
> not ?

Yes, the qapi allows for QMP commands to have a union of secondary
parameters determined by the value of a discriminator key.

-- 
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-01-05 17:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 12:14 [Qemu-devel] More structured migration URIs? Dr. David Alan Gilbert
2015-01-05 12:29 ` Daniel P. Berrange
2015-01-05 12:37   ` Dr. David Alan Gilbert
2015-01-05 12:45     ` Daniel P. Berrange
2015-01-05 14:21       ` Dr. David Alan Gilbert
2015-01-05 17:02       ` Eric Blake [this message]

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=54AAC3AF.4050302@redhat.com \
    --to=eblake@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=berrange@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.