All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	alex@csgraf.de, nolan@sigbus.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add HTTP protocol using curl v2
Date: Wed, 6 May 2009 11:13:24 +0100	[thread overview]
Message-ID: <20090506101324.GE23167@redhat.com> (raw)
In-Reply-To: <20090506100628.GD23167@redhat.com>

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.

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-05-06 10:13 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06  1:00 [Qemu-devel] [PATCH] Add HTTP protocol using curl v2 alex
2009-05-06  8:28 ` Daniel P. Berrange
2009-05-06  9:14   ` Kevin Wolf
2009-05-06  9:31     ` Daniel P. Berrange
2009-05-06  9:40       ` Alexander Graf
2009-05-06  9:57       ` Avi Kivity
2009-05-06 10:00         ` Kevin Wolf
2009-05-06 10:06         ` Daniel P. Berrange
2009-05-06 10:13           ` Daniel P. Berrange [this message]
2009-05-06 10:15             ` Avi Kivity
2009-05-06 10:15             ` Alexander Graf
2009-05-06 13:11               ` Anthony Liguori
2009-05-06 10:16             ` Kevin Wolf
2009-05-06 10:23               ` Alexander Graf
2009-05-06 10:24               ` Daniel P. Berrange
2009-05-06 10:09         ` Alexander Graf
2009-05-06 13:09         ` Anthony Liguori
2009-05-06 13:59           ` Avi Kivity
2009-05-06 14:08             ` Anthony Liguori
2009-05-06 14:14               ` François Revol
2009-05-06 13:12         ` Anthony Liguori
2009-05-06 13:39           ` Daniel P. Berrange
2009-05-06 13:43             ` Anthony Liguori
2009-05-06 13:50             ` Kevin Wolf
2009-05-06 13:59               ` Anthony Liguori
2009-05-06 14:11                 ` Kevin Wolf
2009-05-06 14:39                   ` Anthony Liguori
2009-05-06 14:48                     ` Alexander Graf
2009-05-06 14:49                     ` Avi Kivity
2009-05-06 16:51                       ` Anthony Liguori
2009-05-08 17:00                         ` Jamie Lokier
2009-05-06 14:49                     ` Kevin Wolf
2009-05-06 13:08       ` Anthony Liguori
2009-05-06 10:43     ` Jamie Lokier
2009-05-06 12:59   ` Anthony Liguori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090506101324.GE23167@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex@csgraf.de \
    --cc=avi@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=nolan@sigbus.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.