On Wed, Feb 22, 2012 at 11:17:17AM -0200, Luiz Capitulino wrote: > On Tue, 21 Feb 2012 19:40:16 +0200 > Alon Levy <al...@redhat.com> wrote: > > > On Tue, Feb 21, 2012 at 09:15:45AM -0700, Eric Blake wrote: > > > On 02/21/2012 01:19 AM, Alon Levy wrote: > > > > > > >>> (2) Async monitor command. Keeps interface and works nicely. A > > > >>> bunch > > > >>> of QAPI bits tickled into master meanwhile, so we could look at > > > >>> this again. Luiz? What is the status here? > > The qapi infra is already in place for sometime now, but it doesn't support > async commands yet. However, we're accepting a combination of command + async > event on completion for commands that have to be async. > > We'll eventually have a good interface for async support, but it's not likely > we'll have it for 1.1 (possible, but unlikely). > > I think item 2 above is a good way to go, considering it will add a new > command, > of course. >
Ok, so that sounds good: I'll add an event, and later libvirt/autotest can use it. But in that case I'll need to introduce a connection between the command and the event, some id. That id will have to be generated by the command issuer, so a new command with event id + complete event? > > Luiz said that this interface is going to be dropped, so we don't want > > to introduce another user to it now. > > Please don't :) >
