From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41644) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dX1vL-00066n-08 for qemu-devel@nongnu.org; Mon, 17 Jul 2017 05:02:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dX1vK-0003Pg-7R for qemu-devel@nongnu.org; Mon, 17 Jul 2017 05:02:39 -0400 Date: Mon, 17 Jul 2017 10:02:28 +0100 From: "Daniel P. Berrange" Message-ID: <20170717090228.GE3640@redhat.com> Reply-To: "Daniel P. Berrange" References: <87379zhrhn.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87379zhrhn.fsf@dusky.pond.sub.org> Subject: Re: [Qemu-devel] qapi: Stop abusing "special" values for something entirely different List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: qemu-devel@nongnu.org, Eric Blake , Kevin Wolf , qemu-block@nongnu.org On Fri, Jul 14, 2017 at 07:12:52PM +0200, Markus Armbruster wrote: > Here's what I propose to do: > > 1. Stop abusing values the schema accepts, but are invalid to mean "do > something else entirely". > > 2. Add a first class null type to QAPI. > > 3. Turn MigrationParameters members tls-creds and tls-hostname into > alternate of str and null. Deprecate "". > > 4. Add a null member to alternate BlockdefRef. Deprecate "". > > I got patches for 2., and I intend to work on 3. and 4. > > Since this is "only" about "less than general and ugly", we may decide > to leave things as they are if my patches turn out even uglier. > > Meanwhile, opinions? That sounds ok in principle to me, so worth at least proposing the patches so we can see how it works out in practice. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|