Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2

[Anthony Liguori]

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