mirror of
https://github.com/curl/curl.git
synced 2026-06-30 23:19:16 +03:00
357808f4ad
Add infrastructure to colled and dispatch notifications for transfers and the multi handle in general. Applications can register a callback and en-/disable notification type the are interested in. Without a callback installed, notifications are not collected. Same when a notification type has not been enabled. Memory allocation failures on adding notifications lead to a general multi failure state and result in CURLM_OUT_OF_MEMORY returned from curl_multi_perform() and curl_multi_socket*() invocations. Closes #18432
66 lines
1.5 KiB
Markdown
66 lines
1.5 KiB
Markdown
---
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Title: curl_multi_notify_disable
|
|
Section: 3
|
|
Source: libcurl
|
|
See-also:
|
|
- CURLMOPT_NOTIFYFUNCTION (3)
|
|
- CURLMOPT_NOTIFYDATA (3)
|
|
- curl_multi_notify_enable (3)
|
|
Protocol:
|
|
- All
|
|
Added-in: 8.17.0
|
|
---
|
|
|
|
# NAME
|
|
|
|
curl_multi_notify_disable - disable a notification type
|
|
|
|
# SYNOPSIS
|
|
|
|
~~~c
|
|
#include <curl/curl.h>
|
|
CURLMcode curl_multi_notify_disable(CURLM *multi_handle,
|
|
unsigned int notification);
|
|
~~~
|
|
|
|
# DESCRIPTION
|
|
|
|
Disables collecting the given notification type in the multi handle. A
|
|
callback function installed via CURLMOPT_NOTIFYFUNCTION(3) is no longer
|
|
called when this notification happens.
|
|
|
|
Only when a notification callback is installed *and* a notification
|
|
is enabled are these collected and dispatched to the callback.
|
|
|
|
Several notification types can be enabled at the same time. Disabling
|
|
an already disabled notification is not an error.
|
|
|
|
A notification can be enabled again via curl_multi_notify_enable(3).
|
|
|
|
# %PROTOCOLS%
|
|
|
|
# EXAMPLE
|
|
|
|
~~~c
|
|
int main(void)
|
|
{
|
|
int rc;
|
|
CURLM *multi = curl_multi_init();
|
|
|
|
rc = curl_multi_notify_disable(multi, CURLM_NTFY_INFO_READ);
|
|
}
|
|
~~~
|
|
|
|
# %AVAILABILITY%
|
|
|
|
# RETURN VALUE
|
|
|
|
This function returns a CURLMcode indicating success or error.
|
|
|
|
CURLM_OK (0) means everything was OK, non-zero means an error occurred, see
|
|
libcurl-errors(3).
|
|
|
|
The return code is for the whole multi stack. Problems still might have
|
|
occurred on individual transfers even when one of these functions return OK.
|