curlopt_progressfunction(3) [mojave man page]

CURLOPT_PROGRESSFUNCTION(3)				     curl_easy_setopt options				       CURLOPT_PROGRESSFUNCTION(3)

NAME

       CURLOPT_PROGRESSFUNCTION - callback to progress meter function

SYNOPSIS

       #include <curl/curl.h>

       int progress_callback(void *clientp,
			     double dltotal,
			     double dlnow,
			     double ultotal,
			     double ulnow);

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PROGRESSFUNCTION, progress_callback);

DESCRIPTION

       Pass a pointer to your callback function, which should match the prototype shown above.

       We encourage users to use the newer CURLOPT_XFERINFOFUNCTION(3) instead, if you can.

       This  function  gets called by libcurl instead of its internal equivalent with a frequent interval. While data is being transferred it will
       be called very frequently, and during slow periods like when nothing is being transferred it can slow down to about one call per second.

       clientp is the pointer set with CURLOPT_PROGRESSDATA(3), it is not used by libcurl but is only passed along from  the  application  to  the
       callback.

       The  callback  gets  told how much data libcurl will transfer and has transferred, in number of bytes. dltotal is the total number of bytes
       libcurl expects to download in this transfer. dlnow is the number of bytes downloaded so far. ultotal is the total number of bytes  libcurl
       expects to upload in this transfer. ulnow is the number of bytes uploaded so far.

       Unknown/unused  argument values passed to the callback will be set to zero (like if you only download data, the upload size will remain 0).
       Many times the callback will be called one or more times first, before it knows the data sizes so a program must be made to handle that.

       Returning a non-zero value from this callback will cause libcurl to abort the transfer and return CURLE_ABORTED_BY_CALLBACK.

       If you transfer data with the multi interface, this function will not be called during periods of idleness unless you call the  appropriate
       libcurl function that performs transfers.

       CURLOPT_NOPROGRESS(3) must be set to 0 to make this function actually get called.

DEFAULT

       By default, libcurl has an internal progress meter. That's rarely wanted by users.

PROTOCOLS

       All

EXAMPLE

       https://curl.haxx.se/libcurl/c/progressfunc.html

AVAILABILITY

       Always

RETURN VALUE

       Returns CURLE_OK.

SEE ALSO

       CURLOPT_VERBOSE(3), CURLOPT_NOPROGRESS(3),

libcurl 7.54.0							 February 03, 2016				       CURLOPT_PROGRESSFUNCTION(3)

CURLOPT_READFUNCTION(3) 				     curl_easy_setopt options					   CURLOPT_READFUNCTION(3)

NAME

       CURLOPT_READFUNCTION - read callback for data uploads

SYNOPSIS

       #include <curl/curl.h>

       size_t read_callback(char *buffer, size_t size, size_t nitems, void *instream);

       CURLcode curl_easy_setopt(CURL *handle, CURLOPT_READFUNCTION, read_callback);

DESCRIPTION

       Pass a pointer to your callback function, as the prototype shows above.

       This  callback  function  gets  called  by libcurl as soon as it needs to read data in order to send it to the peer - like if you ask it to
       upload or post data to the server. The data area pointed at by the pointer buffer should be filled up with at  most  size  multiplied  with
       nmemb number of bytes by your function.

       Your  function  must  then return the actual number of bytes that it stored in that memory area. Returning 0 will signal end-of-file to the
       library and cause it to stop the current transfer.

       If you stop the current transfer by returning 0 "pre-maturely" (i.e before the server expected it, like when you've said you will upload  N
       bytes and you upload less than N bytes), you may experience that the server "hangs" waiting for the rest of the data that won't come.

       The  read callback may return CURL_READFUNC_ABORT to stop the current operation immediately, resulting in a CURLE_ABORTED_BY_CALLBACK error
       code from the transfer.

       The callback can return CURL_READFUNC_PAUSE to cause reading from this connection to pause. See curl_easy_pause(3) for further details.

       Bugs: when doing TFTP uploads, you must return the exact amount of data that the callback wants, or it will be considered the final  packet
       by the server end and the transfer will end there.

       If  you	set this callback pointer to NULL, or don't set it at all, the default internal read function will be used. It is doing an fread()
       on the FILE * userdata set with CURLOPT_READDATA(3).

DEFAULT

       The default internal read callback is fread().

PROTOCOLS

       This is used for all protocols when doing uploads.

EXAMPLE

       Here's an example setting a read callback for reading that to upload to an FTP site: https://curl.haxx.se/libcurl/c/ftpupload.html

AVAILABILITY

       CURL_READFUNC_PAUSE return code was added in 7.18.0 and CURL_READFUNC_ABORT was added in 7.12.1.

RETURN VALUE

       This will return CURLE_OK.

SEE ALSO

       CURLOPT_READDATA(3), CURLOPT_WRITEFUNCTION(3), CURLOPT_SEEKFUNCTION(3), CURLOPT_UPLOAD(3), CURLOPT_POST(3),

libcurl 7.54.0							 February 03, 2016					   CURLOPT_READFUNCTION(3)