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: curl_easy_cmdline
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Patrick Schlangen via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 2 Dec 2020 12:44:05 +0100
Am 02.12.2020 um 10:24 schrieb Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>:
>
>> This function will be dead code for any application using libcurl - except for curl itself.
>
> There are probably tens of thousands of authors in the world who are writing applications using the libcurl API. In C, PHP, Python, perl, R and other languages.
>
> They are typically the people who I envision would (perhaps) appreciate this idea.
I like the idea and think it can be very useful, but at the same time I can understand the concern that this code will not be used by many applications which use libcurl.
As especially in embedded environments it might be a goal to keep the library footprint as low as possible, how about adding a compile time option to be able to toggle this feature on/off, with default being 'on'?
(Another mild concern might be that, at least in my understanding, the curl binary uses libcurl, but libcurl doesn't 'know' about the curl application. Hence the dependency is in one direction only. Now we would have to update/adjust libcurl in case we change the command line interface of curl in order to still output a valid command line. Hence it would add a 'soft' dependency in the opposite direction?)
Patrick
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2020-12-02
Date: Wed, 2 Dec 2020 12:44:05 +0100
Am 02.12.2020 um 10:24 schrieb Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>:
>
>> This function will be dead code for any application using libcurl - except for curl itself.
>
> There are probably tens of thousands of authors in the world who are writing applications using the libcurl API. In C, PHP, Python, perl, R and other languages.
>
> They are typically the people who I envision would (perhaps) appreciate this idea.
I like the idea and think it can be very useful, but at the same time I can understand the concern that this code will not be used by many applications which use libcurl.
As especially in embedded environments it might be a goal to keep the library footprint as low as possible, how about adding a compile time option to be able to toggle this feature on/off, with default being 'on'?
(Another mild concern might be that, at least in my understanding, the curl binary uses libcurl, but libcurl doesn't 'know' about the curl application. Hence the dependency is in one direction only. Now we would have to update/adjust libcurl in case we change the command line interface of curl in order to still output a valid command line. Hence it would add a 'soft' dependency in the opposite direction?)
Patrick
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2020-12-02