From: Matthew Booth <mbooth@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Eric Blake <eblake@redhat.com>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Curl updates
Date: Wed, 14 May 2014 12:08:59 -0400 [thread overview]
Message-ID: <5373951B.4080609@redhat.com> (raw)
In-Reply-To: <20140514074817.GB3610@noname.redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 14/05/14 03:48, Kevin Wolf wrote:
> Am 13.05.2014 um 21:47 hat Eric Blake geschrieben:
>> On 05/08/2014 02:42 AM, Matthew Booth wrote:
>>> [PATCH 1/4] curl: Fix parsing of readahead option from
>>> filename [PATCH 2/4] curl: Add sslverify option [PATCH 3/4]
>>> curl: Add usage documentation
>>>
>>> The first 3 patches are reposted with updates following
>>> discussion of the option syntax. With this patch I've decided
>>> to break entirely with the previous syntax. Given that option
>>> parsing was previously both broken and undocumented, this is
>>> hopefully a forgivable sin.
>>>
>>> The new syntax is:
>>>
>>> http://user:password@example.com/path?query[opt1=val:opt2=val]
>>>
>>> I've bounded the option block in square brackets as these have
>>> no semantic meaning in any of the supported URI formats.
>>
>> Offhand, I'm not liking this. Why not use a completely valid
>> URI, with '.../path?query&opt1=val&opt2=val'? Inventing your
>> own [opt1=val:opt2=val] on top of URI is asking for confusion.
>>
>> Are you trying to support a way to pass a query string to the
>> curl URI, in addition to local options? How often do curl URIs
>> need a query?
>
> My guess would be that you need this more often than local
> options.
>
> Anyway, let's not add new options encoded in the URL, but point
> users to separate options. We may decide that we need the support
> the old crude way of encoding local options for compatibility, but
> preferably I would make filename just a plain URL.
Agree, but only when we support giving options to a backing file.
Matt
- --
Matthew Booth
Red Hat Engineering, Virtualisation Team
Phone: +442070094448 (UK)
GPG ID: D33C3490
GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlNzlRsACgkQNEHqGdM8NJD2gQCfcjTTNukAHagZmZ8YIl7NrKxa
n+YAoIju2DbERjV55zc5xt1TtLwOaq6u
=0n8Q
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-05-14 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 8:42 [Qemu-devel] Curl updates Matthew Booth
2014-05-08 8:42 ` [Qemu-devel] [PATCH 1/4] curl: Fix parsing of readahead option from filename Matthew Booth
2014-05-13 17:29 ` Eric Blake
2014-05-14 16:00 ` Matthew Booth
2014-05-14 16:55 ` Eric Blake
2014-05-08 8:42 ` [Qemu-devel] [PATCH 2/4] curl: Add sslverify option Matthew Booth
2014-05-08 8:42 ` [Qemu-devel] [PATCH 3/4] curl: Add usage documentation Matthew Booth
2014-05-08 8:42 ` [Qemu-devel] [PATCH 4/4] curl: Fix build when curl_multi_socket_action isn't available Matthew Booth
2014-05-13 19:47 ` [Qemu-devel] Curl updates Eric Blake
2014-05-14 7:48 ` Kevin Wolf
2014-05-14 12:59 ` Eric Blake
2014-05-14 16:08 ` Matthew Booth [this message]
2014-05-14 16:43 ` Kevin Wolf
2014-05-14 21:20 ` Matthew Booth
2014-05-14 21:36 ` Eric Blake
2014-05-14 16:59 ` Eric Blake
2014-05-14 16:06 ` Matthew Booth
2014-05-14 17:02 ` Eric Blake
2014-05-14 20:45 ` Matthew Booth
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=5373951B.4080609@redhat.com \
--to=mbooth@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=peter.maydell@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).