From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:53520)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1btzz0-0003dR-DQ
	for qemu-devel@nongnu.org; Tue, 11 Oct 2016 12:32:51 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <armbru@redhat.com>) id 1btzyz-0007Le-IW
	for qemu-devel@nongnu.org; Tue, 11 Oct 2016 12:32:50 -0400
From: Markus Armbruster <armbru@redhat.com>
References: <cover.1475757437.git.berto@igalia.com>
	<1c8e6e73084e968514b6522576cfacd1bf69609e.1475757437.git.berto@igalia.com>
	<48b78d7e-3f52-79d3-27a1-19047100161b@redhat.com>
	<w51wphf0xh2.fsf@maestria.local.igalia.com>
	<20161011145712.GF6334@noname.redhat.com>
Date: Tue, 11 Oct 2016 18:32:39 +0200
In-Reply-To: <20161011145712.GF6334@noname.redhat.com> (Kevin Wolf's message
	of "Tue, 11 Oct 2016 16:57:12 +0200")
Message-ID: <878ttu9788.fsf@dusky.pond.sub.org>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Qemu-devel] [PATCH v10 09/16] block: Add QMP support for
 streaming to an intermediate layer
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: Kevin Wolf <kwolf@redhat.com>
Cc: Alberto Garcia <berto@igalia.com>, qemu-block@nongnu.org, qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>

Kevin Wolf <kwolf@redhat.com> writes:

> Am 11.10.2016 um 16:30 hat Alberto Garcia geschrieben:
[...]
>> 3) QEMU could advertise that feature to the client. This is probably
>> simpler than trying to figure it out from the API. I guess that's the
>> idea of 'qmp_capabilities'?
>
> I think that was the idea, though it was never used. If we had used it,
> I'm not sure how long the capabilities list would be today. :-)

QMP capabilities are for changes in the QMP protocol, not for changes in
commands, events and types.  The protocol has been good enough so far,
thus no capabilities.