Anthony Liguori wrote: > 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.
We can't libvirt talk QMG with Python over a pipe or local socket? So that the Python can talk to native qemu and via libvirt with the same code. That would be much easier from Python person than writing a wrapper around the C library. Multiplied by each high-level language... -- Jamie -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
