|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] Re: [RFC][PATCH v1 05/12] qapi: fix handling for null-return async callbacks |
Date: | Mon, 28 Mar 2011 12:39:15 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8 |
On 03/28/2011 12:27 PM, Luiz Capitulino wrote:
We had to make a choice. We chose the current 'return' response. Iirc, one of my first suggestions was "{ 'return': 'null' }"
It would be: { 'return': null } That's the valid JSON version.
but you refused to have a 'null' object, our parser doesn't even support it afaik.
It doesn't but that's because there isn't a QNone.
But what's the problem with the current format?
Nothing, I was mostly curious as I only vaguely remember this discussion previously.
Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |