From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:54557) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJ3PB-0000fA-5V for qemu-devel@nongnu.org; Tue, 02 Oct 2012 10:25:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TJ3P1-0004dp-Nr for qemu-devel@nongnu.org; Tue, 02 Oct 2012 10:25:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7116) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJ3P1-0004dj-F1 for qemu-devel@nongnu.org; Tue, 02 Oct 2012 10:24:51 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q92EOodE018145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 2 Oct 2012 10:24:50 -0400 Message-ID: <506AF930.7000902@redhat.com> Date: Tue, 02 Oct 2012 16:24:48 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1349103144-6827-1-git-send-email-pbonzini@redhat.com> <1349103144-6827-3-git-send-email-pbonzini@redhat.com> <506A2D98.4080300@redhat.com> <506AAD22.5040305@redhat.com> <506AD288.7010204@redhat.com> <20121002092727.1a1cf31d@doriath.home> In-Reply-To: <20121002092727.1a1cf31d@doriath.home> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 2/9] qapi: add socket address types List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: Eric Blake , qemu-devel@nongnu.org Il 02/10/2012 14:27, Luiz Capitulino ha scritto: >>>> > >> for a port range, all because of the possibility of named ports; should >>>> > >> '*to' be a 'str' if only for symmetry in the output? But it's >>>> > >> bike-shedding, so I'll live with whatever works (that is, I'm not >>>> > >> requesting a v3 on this patch). >>> > > >>> > > Would it be better if I changed 'to' to 'count'? >> > >> > That does look a little better: >> > >> > 'host':'localhost', 'port':'1000', 'count':2 >> > >> > for the 2-port range 1000-1001. But it's all the same information, so >> > I'm not strongly tied to any particular representation, as long as >> > libvirt can parse it when querying and produce it when starting NBD. > Wouldn't it be cleaner to pass a list of port numbers? We could have: > > *port-list: [ 'int' ] > *service: 'str' A list of ports doesn't work too well for say 5900-5999. I think the port + count is the simplest. Paolo