From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:35393)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1UUGCm-0006H6-5f
	for qemu-devel@nongnu.org; Mon, 22 Apr 2013 08:50:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1UUGCk-00066g-9r
	for qemu-devel@nongnu.org; Mon, 22 Apr 2013 08:50:47 -0400
Received: from mx1.redhat.com ([209.132.183.28]:12566)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <lcapitulino@redhat.com>) id 1UUGCj-00066U-SB
	for qemu-devel@nongnu.org; Mon, 22 Apr 2013 08:50:46 -0400
Date: Mon, 22 Apr 2013 08:50:43 -0400
From: Luiz Capitulino <lcapitulino@redhat.com>
Message-ID: <20130422085043.4a3e891c@redhat.com>
In-Reply-To: <517504CB.6040303@redhat.com>
References: <1366275680-15416-1-git-send-email-kraxel@redhat.com>
	<87ppxq6hmn.fsf@blackfin.pond.sub.org> <5174DEE5.20406@redhat.com>
	<517504CB.6040303@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RfC PATCH 0/5] console: qom-ify & extent
 screendump monitor command
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, aliguori@us.ibm.com, Gerd Hoffmann <kraxel@redhat.com>, Markus Armbruster <armbru@redhat.com>

On Mon, 22 Apr 2013 11:37:15 +0200
Paolo Bonzini <pbonzini@redhat.com> wrote:

> Il 22/04/2013 08:55, Gerd Hoffmann ha scritto:
> >>> >> Question for the libvirt guys:  Is it ok for libvirt to just extend the
> >>> >> existing screendump command?  Can libvirt figure there is a new
> >>> >> (optional) parameter?  See patch #5.
> >> > 
> >> > Nope, QMP can't do that.  I argued for such capabilities, but the
> >> > "create a new command" philosophy prevailed.
> >> > 
> >> > Go forth and multiply commands!  And have fun picking command names that
> >> > aren't fugly.
> > Oh joy.  Lets just enumerate things & use "screendump2" ...
> 
> QMP can't do that _yet_.
> 
> Let's fix it instead...

The point is that we have chosen not to do so a while ago. In a nutshell,
Anthony thinks that we should have the same compatibility contract of
a C API.