On 05/14/2014 10:06 AM, Matthew Booth wrote: >>> The new syntax is: >>> >>> http://user:passw...@example.com/path?query[opt1=val:opt2=val] >>>
>
> A URI can, by definition, contain a query string, and we cannot assume
> that it won't. In fact, the use case I'm specifically interested in
> always includes a query string. If we try to overload the query
> string, we're adding heuristic fuzziness. My syntax makes the option
> string distinct from the URI, so no heuristics are required. It's also
> very clear to read IMHO.
But your proposed syntax is no longer a URI. I'd much rather see:
'json:{"driver":"curl","filename":"http://user:passw...@example.com/path?query","opt1":"val","opt2":"val"}'
which then shares the same syntax as all other drivers for creating a
flat string that encodes multiple pieces of information, rather than
having to overload the filename to be a non-URI encoding locally useful
information.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
