On 04/24/2013 03:59 PM, Eric Blake wrote:
> With full-blown command introspection, we would want to be asking for a
> JSON representation more details about each parameter, in a struct that
> looks something like { 'name':'str', 'type':'<enumOfTypes>',
> 'optional':'boolean', '*default':'<typesafe way of representing the
> default of any boolean option>', '*documentation':'str' }. If we don'ts/boolean option/optional parameter/ > provide filtering, then this JSON output might be quite large, because > it covers all QMP commands, > Whatever we do for full-blown introspection will probably end up quite similar to what we do for command-line introspection; for those following along (bikeshedding on the naming is still happening, but the idea of a struct per command-line option is pretty much agreed on): https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg04929.html -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
