From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35096)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1VcFMs-0005Fb-Cf
	for qemu-devel@nongnu.org; Fri, 01 Nov 2013 10:06:36 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1VcFMm-00085S-Dl
	for qemu-devel@nongnu.org; Fri, 01 Nov 2013 10:06:30 -0400
Received: from mx1.redhat.com ([209.132.183.28]:43521)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1VcFMm-00084L-4z
	for qemu-devel@nongnu.org; Fri, 01 Nov 2013 10:06:24 -0400
Date: Fri, 1 Nov 2013 10:06:19 -0400
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20131101100619.509936a1@redhat.com>
In-Reply-To: <526FDDC4.9010803@redhat.com>
References: <1382321765-29052-1-git-send-email-xiawenc@linux.vnet.ibm.com>
	<1382321765-29052-4-git-send-email-xiawenc@linux.vnet.ibm.com>
	<5265917D.3000903@redhat.com> <526E3FF1.7060305@redhat.com>
	<526F4631.50706@linux.vnet.ibm.com> <526FDDC4.9010803@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH 3/6] qapi: rename prefix QEVENT to Q_EVENT
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/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: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, armbru@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com, Paolo Bonzini <pbonzini@redhat.com>, Wenchao Xia <xiawenc@linux.vnet.ibm.com>

On Tue, 29 Oct 2013 10:09:40 -0600
Eric Blake <eblake@redhat.com> wrote:

> On 10/28/2013 11:22 PM, Wenchao Xia wrote:
> 
> >>
> >   MONITOR_EVENT seems tide to monitor too much, since it will be present
> > in qapi-schema, I think Q_EVENT_ or QMP_EVENT_KIND would be better?
> 
> I don't have a strong enough opinion on the bikeshed color.
> MONITOR_EVENT implies the event is always associated with delivery over
> a monitor; but how else would you receive an event without a monitor?

Today QMP is tied to the Monitor, but one of the goals of the QAPI is
to untangle them. This would allow for a separate QMP server, which
could have QMP only features like session support.