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: A feature request
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Sat, 19 Mar 2022 09:06:13 -0700
On Sat, Mar 19, 2022 at 01:06:53PM +0530, Devang Modi via curl-library wrote:
> I m working on a project that is based upon PROGRESS/OpenEdge software.
> I am looking to integrate libCurl for this project but due to the native
> platform language support issue
> I am not able to use the following feature of libCurl.
> Features are
>
> curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, *); curl_easy_setopt(curl,
> CURLOPT_WRITEDATA, *); curl_easy_setopt(curl, CURLOPT_READFUNCTION, *);
> curl_easy_setopt(curl, CURLOPT_READDATA, *); This issue is very simple and
> that is native language call PROGRESS 4GL does not support function memory
> pointer fetching feature. In option to this Is it possible that you can add
> two more OPTIONS like CURLOPT_FILEWRITE that receives FILEHANDLE and write all
> outcomes to the given filehandle after a successful connection takes place.
This is how libcurl works already! See CURLOPT_WRITEDATA.
> similar way CURLOPT_FILEREAD receives FILEHANDLE and reads and transmits data
> from the given filehandle after a successful connection happens. It is not
> mandatory but the same kind of feature can be added for debugging the outcome
> files. CURLOPT_DEBUGFILE receives FILEHANDLE and writes all debug information
> to the given filehandle after a successful connection takes place. Please
> share your view and advice on this, thanks Devang
Unfortunately, CURLOPT_DEBUGDATA doesn't work the same way by default. But,
whatever language binding you are using ought to have the capability of setting
up a function pointer at the C level for your application. And if the language
binding doesn't do that for you, you can always write a simple shim library
that does it which that the application can load instead of libcurl.so or
libcurl.dll.
Dan
Date: Sat, 19 Mar 2022 09:06:13 -0700
On Sat, Mar 19, 2022 at 01:06:53PM +0530, Devang Modi via curl-library wrote:
> I m working on a project that is based upon PROGRESS/OpenEdge software.
> I am looking to integrate libCurl for this project but due to the native
> platform language support issue
> I am not able to use the following feature of libCurl.
> Features are
>
> curl_easy_setopt(curl, CURLOPT_WRITEFUNCTION, *); curl_easy_setopt(curl,
> CURLOPT_WRITEDATA, *); curl_easy_setopt(curl, CURLOPT_READFUNCTION, *);
> curl_easy_setopt(curl, CURLOPT_READDATA, *); This issue is very simple and
> that is native language call PROGRESS 4GL does not support function memory
> pointer fetching feature. In option to this Is it possible that you can add
> two more OPTIONS like CURLOPT_FILEWRITE that receives FILEHANDLE and write all
> outcomes to the given filehandle after a successful connection takes place.
This is how libcurl works already! See CURLOPT_WRITEDATA.
> similar way CURLOPT_FILEREAD receives FILEHANDLE and reads and transmits data
> from the given filehandle after a successful connection happens. It is not
> mandatory but the same kind of feature can be added for debugging the outcome
> files. CURLOPT_DEBUGFILE receives FILEHANDLE and writes all debug information
> to the given filehandle after a successful connection takes place. Please
> share your view and advice on this, thanks Devang
Unfortunately, CURLOPT_DEBUGDATA doesn't work the same way by default. But,
whatever language binding you are using ought to have the capability of setting
up a function pointer at the C level for your application. And if the language
binding doesn't do that for you, you can always write a simple shim library
that does it which that the application can load instead of libcurl.so or
libcurl.dll.
Dan
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-03-19