From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MqnUY-0005h7-BP
	for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:32:10 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MqnUS-0005fW-1v
	for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:32:08 -0400
Received: from [199.232.76.173] (port=54145 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MqnUQ-0005ej-IO
	for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:32:03 -0400
Received: from mx1.redhat.com ([209.132.183.28]:6268)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <lcapitulino@redhat.com>) id 1MqnUN-0007fG-So
	for qemu-devel@nongnu.org; Thu, 24 Sep 2009 08:32:01 -0400
Date: Thu, 24 Sep 2009 09:31:46 -0300
From: Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] ANN: QEMU Monitor Protocol git tree
Message-ID: <20090924093146.66191c37@doriath>
In-Reply-To: <87my4l1e4e.fsf@pike.pond.sub.org>
References: <20090921224430.610da97b@doriath>
	<87my4l1e4e.fsf@pike.pond.sub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
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.gnu.org/pipermail/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: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com

On Thu, 24 Sep 2009 00:37:53 +0200
Markus Armbruster <armbru@redhat.com> wrote:

> Luiz Capitulino <lcapitulino@redhat.com> writes:
> 
> [...]
> > 2.2 Server Greeting
> > -------------------
> >
> > Right when connected the Server will issue a greeting message, which signals
> > that the connection has been successfully established and that the Server is
> > waiting for commands.
> >
> > The format is:
> >
> > { "QEMU": json-string, "QMP": json-string, "capabilities": json-array }
> >
> >  Where,
> >
> > - The "QEMU" member contains the QEMU version
> > - The "QMP" member contains the QMP version
> > - The "capabilities" member specify the availability of features beyond the
> >   baseline specification
> 
> What about capability negotiation?  Server offers capabilities, client
> can accept or decline them.
> 
> [...]

 I think the easiest way to have this would be to add a
monitor command to disable capabilities. Like a command to
disable async messages.