Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Proposal: URL API extension, second setter function to allow setting from CURLU object
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Timothe Litt <litt_at_acm.org>
Date: Mon, 23 Oct 2023 11:10:01 -0400
On 23-Oct-23 08:28, Mark Gaiser via curl-library wrote:
> On Mon, Oct 23, 2023 at 8:57 AM Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Sun, 22 Oct 2023, Mark Gaiser via curl-library wrote:
>
> > I get that this is c-code and just the c-way of doing things.
> Still, it can
> > be simplified a lot, even in c.
> >
> > I propose a new URL API function with the following signature:
> > CURLUcode curl_url_set_o(CURLU *u, CURLUPart what,
> > const CURLU *source, unsigned int flags)
>
> Assuming you write a lot of code that cherry-picks components from
> one URL and
> copies them into another, then this looks likes a shortcut yes.
> But it also
> looks like a kind of function you can easily implement yourself,
> using
> libcurl's API, in about twenty lines of code or so.
>
>
> I'm not firmly against introducing a function like this, but I
> think it is
> rather specific for a single use case that might not be what most
> URL API
> users ever need.
>
>
> Thank you for your insights!
> If anyone knows curl, it's you :)
>
> If you think this is probably too specific then it probably is.
>
> If anyone else is interested or knows use cases, share your opinion here.
> Else it's gonna stay as an idea to slowly fade away into the corners
> of the mailing list.
>
If you need more than libcurl's features for manipulating URIs, there
are other C libraries that are widely available, e.g.
https://uriparser.github.io/ (https://github.com/uriparser/uriparser)
Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
Received on 2023-10-23
Date: Mon, 23 Oct 2023 11:10:01 -0400
On 23-Oct-23 08:28, Mark Gaiser via curl-library wrote:
> On Mon, Oct 23, 2023 at 8:57 AM Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Sun, 22 Oct 2023, Mark Gaiser via curl-library wrote:
>
> > I get that this is c-code and just the c-way of doing things.
> Still, it can
> > be simplified a lot, even in c.
> >
> > I propose a new URL API function with the following signature:
> > CURLUcode curl_url_set_o(CURLU *u, CURLUPart what,
> > const CURLU *source, unsigned int flags)
>
> Assuming you write a lot of code that cherry-picks components from
> one URL and
> copies them into another, then this looks likes a shortcut yes.
> But it also
> looks like a kind of function you can easily implement yourself,
> using
> libcurl's API, in about twenty lines of code or so.
>
>
> I'm not firmly against introducing a function like this, but I
> think it is
> rather specific for a single use case that might not be what most
> URL API
> users ever need.
>
>
> Thank you for your insights!
> If anyone knows curl, it's you :)
>
> If you think this is probably too specific then it probably is.
>
> If anyone else is interested or knows use cases, share your opinion here.
> Else it's gonna stay as an idea to slowly fade away into the corners
> of the mailing list.
>
If you need more than libcurl's features for manipulating URIs, there
are other C libraries that are widely available, e.g.
https://uriparser.github.io/ (https://github.com/uriparser/uriparser)
Timothe Litt
ACM Distinguished Engineer
--------------------------
This communication may not represent the ACM or my employer's views,
if any, on the matters discussed.
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- application/pgp-signature attachment: OpenPGP digital signature