From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=42672 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PzuH2-0006Ot-Qh
	for qemu-devel@nongnu.org; Wed, 16 Mar 2011 13:12:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1PzuFm-0003Jk-FZ
	for qemu-devel@nongnu.org; Wed, 16 Mar 2011 13:11:23 -0400
Received: from mx1.redhat.com ([209.132.183.28]:13131)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <pbonzini@redhat.com>) id 1PzuFm-0003Im-2V
	for qemu-devel@nongnu.org; Wed, 16 Mar 2011 13:11:22 -0400
Message-ID: <4D80E5F0.3020302@redhat.com>
Date: Wed, 16 Mar 2011 17:31:44 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH 00/15] QAPI Round 1 (core code generator)
	(v2)
References: <1299884745-521-1-git-send-email-aliguori@us.ibm.com>	<20110316113428.21c599a3@doriath>
	<4D80CE17.7010005@redhat.com> <4D80DF60.1000703@codemonkey.ws>
In-Reply-To: <4D80DF60.1000703@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Anthony Liguori <aliguori@us.ibm.com>, Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>, Adam Litke <agl@us.ibm.com>, Luiz Capitulino <lcapitulino@redhat.com>

On 03/16/2011 05:03 PM, Anthony Liguori wrote:
> So for an event, you just need to do:
>
> { 'signal': 'vnc-connected', 'data': { 'client': 'VncClientInfo' } }
>
> And you can add new fields to the VncClientInfo structure as much as
> you'd like without worrying about breaking the C ABI.

So why couldn't you automatically wrap the events data field in a 
structure (e.g. vnc-connected events receive a VncConnectedEventData*)?

Paolo