Hi
On Fri, Mar 23, 2018 at 6:18 AM, Peter Xu wrote:
> On Thu, Mar 22, 2018 at 11:22:14AM +0100, Marc-André Lureau wrote:
>> Hi
>>
>> On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
>> > Having "allow-oob" to true for a command does not mean that this command
>> > will always be run in out-of-ba
On Thu, Mar 22, 2018 at 11:22:14AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> > Having "allow-oob" to true for a command does not mean that this command
> > will always be run in out-of-band mode. The out-of-band quick path will
> > only be execut
Hi
On Fri, Mar 9, 2018 at 10:00 AM, Peter Xu wrote:
> Having "allow-oob" to true for a command does not mean that this command
> will always be run in out-of-band mode. The out-of-band quick path will
> only be executed if we specify the extra "run-oob" flag when sending the
> QMP request:
>
>
On 03/09/2018 03:00 AM, Peter Xu wrote:
Having "allow-oob" to true for a command does not mean that this command
s/to/:/
will always be run in out-of-band mode. The out-of-band quick path will
only be executed if we specify the extra "run-oob" flag when sending the
QMP request:
{ "exec
Having "allow-oob" to true for a command does not mean that this command
will always be run in out-of-band mode. The out-of-band quick path will
only be executed if we specify the extra "run-oob" flag when sending the
QMP request:
{ "execute": "command-that-allows-oob",
"arguments": {
