From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41607) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzXqT-0004VB-E2 for qemu-devel@nongnu.org; Fri, 02 Sep 2011 13:48:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QzXqR-0004EJ-En for qemu-devel@nongnu.org; Fri, 02 Sep 2011 13:48:01 -0400 Received: from david.siemens.de ([192.35.17.14]:16819) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzXqR-0004E5-4I for qemu-devel@nongnu.org; Fri, 02 Sep 2011 13:47:59 -0400 Message-ID: <4E6116CB.6010703@siemens.com> Date: Fri, 02 Sep 2011 19:47:55 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <20110902142302.506bf6d0@doriath> In-Reply-To: <20110902142302.506bf6d0@doriath> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 3/6] QMP: Reserve namespace for complex object classes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Anthony Liguori , qemu-devel On 2011-09-02 19:23, Luiz Capitulino wrote: > On Fri, 26 Aug 2011 16:48:13 +0200 > Jan Kiszka wrote: > >> This reserves JSON objects that contain the key '__class__' for QMP-specific >> complex objects. First user will be the buffer class. >> >> CC: Luiz Capitulino >> Signed-off-by: Jan Kiszka >> --- >> QMP/qmp-spec.txt | 16 +++++++++++++--- >> 1 files changed, 13 insertions(+), 3 deletions(-) >> >> diff --git a/QMP/qmp-spec.txt b/QMP/qmp-spec.txt >> index 9d30a8c..fa1dd62 100644 >> --- a/QMP/qmp-spec.txt >> +++ b/QMP/qmp-spec.txt >> @@ -146,6 +146,15 @@ The format is: >> For a listing of supported asynchronous events, please, refer to the >> qmp-events.txt file. >> >> +2.6 Complex object classes >> +-------------------------- >> + >> +JSON objects that contain the key-value pair '"__class__": json-string' are >> +reserved for QMP-specific complex object classes that. QMP specifies which > > Can I just drop the period or is it misplaced? Actually, 'that' is misplaced. > >> +further keys each of these objects include and how they are encoded. >> + >> +So far, no complex object class is specified. >> + Thanks, Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux