We use the uriparser library Radu Hociung mentioned primarily because there
was nothing analogous in curl.

The setters would be important to us. I might be bikeshedding here, but the
ability to add to the query would be very nice. So something like
curl_url_query_append(urlp, "numitems", 3)

An unsigned type feels more appropriate for port than int does.

While I can't say that we'd move our working code from uriparser to this
API, I'm certain this API would have prevented us from reaching for
uriparser in the first place, particularly because all of our URL usage is
for consumption by libcurl anyway.

I assume this is obvious, but if this API gets added to curl, a setopt that
takes a CURLURL would be wanted :)

On Thu, Aug 2, 2018 at 8:41 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Wed, 1 Aug 2018, Radu Hociung wrote:
>
> a "URL handling" API in libcurl
>>>
>>
>> This wheel has already been invented. [1]
>>
>> [1] https://uriparser.github.io/
>>
>
> Are you suggesting this uses an API that would be worth getting
> inspiration from? Personally I don't see a lot I like there...
>
> (Dan already presented some reasons why having our own makes sense.)
>
> --
>
> / 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