From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M1gui-0005Z5-T1 for qemu-devel@nongnu.org; Wed, 06 May 2009 09:11:56 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M1gud-0005XE-Tu for qemu-devel@nongnu.org; Wed, 06 May 2009 09:11:56 -0400 Received: from [199.232.76.173] (port=34419 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M1gud-0005X5-NI for qemu-devel@nongnu.org; Wed, 06 May 2009 09:11:51 -0400 Received: from qw-out-1920.google.com ([74.125.92.144]:46407) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M1gud-0000vB-Cj for qemu-devel@nongnu.org; Wed, 06 May 2009 09:11:51 -0400 Received: by qw-out-1920.google.com with SMTP id 4so59051qwk.4 for ; Wed, 06 May 2009 06:11:50 -0700 (PDT) Message-ID: <4A018C93.1090106@codemonkey.ws> Date: Wed, 06 May 2009 08:11:47 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 References: <1241571650-16212-1-git-send-email-alex@csgraf.de> <20090506082810.GB23167@redhat.com> <4A0154E9.7020705@redhat.com> <20090506093143.GC23167@redhat.com> <4A015F06.7050102@redhat.com> <20090506100628.GD23167@redhat.com> <20090506101324.GE23167@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Kevin Wolf , nolan@sigbus.net, Avi Kivity , qemu-devel@nongnu.org Alexander Graf wrote: > > On 06.05.2009, at 12:13, Daniel P. Berrange wrote: > >> On Wed, May 06, 2009 at 11:06:28AM +0100, Daniel P. Berrange wrote: >>> On Wed, May 06, 2009 at 12:57:26PM +0300, Avi Kivity wrote: >>>> Daniel P. Berrange wrote: >>>>> Then I'd prefer we add a protocol=XXX option for magic protocols. >>>>> This >>>>> would be easier to use & clearer than requiring escaping of magic >>>>> characters, eg >>>>> >>>>> -drive file=/some/path:with:colons,protocol=file >>>>> -drive file=http://some/path,protocol=uri >>>>> >>>>> For compatability, we could make it such that if protocol=XXX was >>>>> left out, >>>>> it could try and "guess" it, in same way QEMU does if format=XXX >>>>> is left >>>>> out >>>>> for content format. >>>>> >>>> >>>> How about >>>> >>>> -drive file=file:///some/path:with:colons? >>>> >>>> Libvirt would use this unconditionally, command-line users can choose. >>> >>> Sure, that achieves the same end result, so fine by me. >> >> Oh and if you want to be really nice, you could say that any filename >> with a leading '/' is implicitly file:///, since I can't imagine >> any protocol name starting with a '/'. And this would ensure any >> existing usage with absolute filenames 'just works' without tripping >> up on colons. > > No, "the right way" would be to always assume file:// for filenames > that don't have a protocol ("://") specified. nbd doesn't use '://'. It's prohibitively hard to express a unix domain socket and parameters with a standard URI. Regards, Anthony Liguori > Alex > > >