From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NLKMa-0007qt-KO for qemu-devel@nongnu.org; Thu, 17 Dec 2009 12:42:08 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NLKMV-0007nR-Li for qemu-devel@nongnu.org; Thu, 17 Dec 2009 12:42:08 -0500 Received: from [199.232.76.173] (port=55629 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NLKMV-0007nL-CM for qemu-devel@nongnu.org; Thu, 17 Dec 2009 12:42:03 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55233) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NLKMU-00075g-DS for qemu-devel@nongnu.org; Thu, 17 Dec 2009 12:42:02 -0500 Date: Thu, 17 Dec 2009 15:41:47 -0200 From: Luiz Capitulino Message-ID: <20091217154147.22845395@doriath> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] QMP's success response List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: aliguori@linux.vnet.ibm.com, armbru@redhat.com, avi@redhat.com Hi there, Currently, when a regular command doesn't have any data to output, QMP will emit: { "return": "OK" } I thought this was a good idea because it has a clear meaning. Silly me, this is optimized for humans, but for machines it introduces the problem that such commands can't be changed to return values. I'm not sure this is will ever happen, but to stay safe a better way would be to return an empty dict, like this: { "return": {} } Which can be read as 'command succeeded, but didn't return any data'. As the release is not done yet we still can change it, is anyone against?