[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] QMP forward compatibility support
From: |
Jamie Lokier |
Subject: |
Re: [Qemu-devel] QMP forward compatibility support |
Date: |
Thu, 14 Jan 2010 00:01:39 +0000 |
User-agent: |
Mutt/1.5.13 (2006-08-11) |
Markus Armbruster wrote:
> It should be optional if we want to support clients that don't want it.
> I don't think coping with it would be a terrible burden on clients, but
> neither is having to ask for it. Personally, I'd make it optional.
It wouldn't be a terrible burden, but it'll be easier to write "quick
and dirty" synchronous clients if they know they don't have to
continuously consume output, to make sure the pipe doesn't fill up,
except immediately after they send a command they wait for the response.
So I'd make async responses optional too.
By quick and dirty, I am talking about one-liner Perl invocations in
shell scripts which control a qemu instance. Something which is easy
with multi-monitor support :-)
-- Jamie
- Re: [Qemu-devel] QMP forward compatibility support, (continued)
- Re: [Qemu-devel] QMP forward compatibility support, Daniel P. Berrange, 2010/01/11
- Re: [Qemu-devel] QMP forward compatibility support, Luiz Capitulino, 2010/01/11
- Re: [Qemu-devel] QMP forward compatibility support, Luiz Capitulino, 2010/01/12
- Re: [Qemu-devel] QMP forward compatibility support, Markus Armbruster, 2010/01/13
- Re: [Qemu-devel] QMP forward compatibility support, Luiz Capitulino, 2010/01/13
- Re: [Qemu-devel] QMP forward compatibility support, Markus Armbruster, 2010/01/13
- Re: [Qemu-devel] QMP forward compatibility support, Luiz Capitulino, 2010/01/13
- Re: [Qemu-devel] QMP forward compatibility support,
Jamie Lokier <=