On Wed, Aug 1, 2018 at 3:19 PM Daniel Stenberg <daniel_at_haxx.se> wrote:

> Hi,
>
> In the 2018 user survey, more than 40% of the 395 users who answered the
> question said they'd use a "URL handling" API in libcurl if one existed.
>
> I gave it some thoughts the other day and I've now jotted down my initial
> suggestion on how it could be made to work. An API that can parse a URL,
> extract the individual pieces, allow the user to set individual parts and
> finally to get the full URL out from there again.

In case this is interesting, I’ve used
https://github.com/nodejs/http-parser in a similar capacity in the past.
It’s been a while since I’ve used it, and I haven’t done a comparison
between your proposal and it, but figured “before i forget... I’d better
send this”. Obviously not fully integrated w cURL, but if there’s good
reference material...

-bch

>
> Here's my thoughts:
>
> https://github.com/curl/curl/wiki/URL-API
>
> Good or bad? What would your application need and would this work for
> that? If
> not, how should we change it to make it better?
>
> (There's no promise that this will ever actually get implemented, but if
> we
> can come up with a proposal we believe in, I don't think there needs to be
> anything stopping it from happening...)
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
> Etiquette: https://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2018-08-02