qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in li


From: Anthony Liguori
Subject: Re: [Qemu-devel] Re: [libvirt] Supporting hypervisor specific APIs in libvirt
Date: Thu, 25 Mar 2010 10:59:22 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Lightning/1.0pre Thunderbird/3.0

On 03/25/2010 09:09 AM, Luiz Capitulino wrote:

We can provide a generic QMP dispatch interface that high level
languages can use.  Then they can do fancy dispatch, treat QErrors as
exceptions, etc.
  They can do that by accessing QMP directly. Why would a Python developer
get in the mess of writing a Python binding for libqemu if they call do
the exactly same thing by using its native json module?

  Man, opening a QMP connection from Python and sending commands can be
done with a few lines.

Problem is, without a libqemu, libvirt cannot return a QMPContext that can be used by python bindings. This is the problem that all high level languages have with respect to RPC transports.

You need libqemu to deal with establishing the transport. That code needs to be common and shared across languages.

Dispatch can be handled by the high level language.

We just ought to also provide some simple C wrappers for all of the
functions.  Yes, the C interface is inferior to the generic interface
but that's fine.
  Why don't we start with my simple lib suggestion and wait one or two
releases to see what happens?

I have no problem starting without the generated C wrappers. But we need the core library to have the right abstractions with respect to transports.

Regards,

Anthony Liguori




reply via email to

[Prev in Thread] Current Thread [Next in Thread]