gnurl_multi_remove_handle(3)

💖 gnurl_multi_remove_handle(3) 💖

okay so this lil page is from the libgnurl Manual, and it's here to explain how to take one easy_handle out of a multi_handle. bestie, it's giving “breakup but make it API” 💅.

🌸 NAME 🌸

curl_multi_remove_handle — remove an easy handle from a multi session.

🦋 SYNOPSIS 🦋

#include <gnurl/curl.h>

CURLMcode curl_multi_remove_handle(CURLM *multi_handle, CURL *easy_handle);

💅 DESCRIPTION 💅

So like, curl_multi_remove_handle removes a given easy_handle from the multi_handle. that means the specified easy handle is no longer under this multi handle's control. slay, boundaries ✨.

Once the easy handle has been removed from a multi stack, it is again perfectly legal to invoke curl_easy_perform(3) on this easy handle. no cap, you can go solo again 🫶.

Removing an easy handle while it's being used is perfectly legal, and it will effectively halt the transfer in progress involving that easy handle. every other easy handle and transfer stays unaffected. the way that one transfer gets stopped but everyone else stays unbothered? iconic 💀✨.

It is fine to remove a handle at any time during a transfer, just not from within any libcurl callback function. like, any time is cute, except that one callback moment — that's the vibe check you don't pass 🙈.

⚠️ bestie, fr fr: don't call this from inside any libcurl callback function. anywhere else during a transfer is fine.

🎀 RETURN VALUE 🎀

It returns the CURLMcode type, the general libcurl multi interface error code. that's the whole return tea ☕.

🌈 SEE ALSO 🌈

• curl_multi_cleanup(3)
• curl_multi_init(3)
• curl_multi_add_handle(3)

okurrr, source check: this page is from libcurl 7.9.5, dated 6 March 2002, and the manual page is literally gnurl_multi_remove_handle(3). bye bestie, go remove those handles responsibly 🎀🦋💜.