From ebb5e1db4b0a3cb1061ac992d615ad0bdadf2fd7 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Sat, 26 May 2007 20:50:00 +0000 Subject: Clarify a bit about the fact that easy handles remain in the multi stack when transfers are done and need to be removed and closed or re-added. --- docs/libcurl/libcurl-multi.3 | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/libcurl/libcurl-multi.3') diff --git a/docs/libcurl/libcurl-multi.3 b/docs/libcurl/libcurl-multi.3 index 9afb107ed..9b36212e1 100644 --- a/docs/libcurl/libcurl-multi.3 +++ b/docs/libcurl/libcurl-multi.3 @@ -104,6 +104,12 @@ get more messages until the message queue is empty. The information you receive there includes an easy handle pointer which you may use to identify which easy handle the information regards. +When a single transfer is completed, the easy handle is still left added to +the multi stack. You need to first remove the easy handle with +\fIcurl_multi_remove_handle(3)\fP and then close it with +\fIcurl_easy_cleanup(3)\fP, or possibly set new options to it and add it again +with \fIcurl_multi_add_handle(3)\fP to start another transfer. + When all transfers in the multi stack are done, cleanup the multi handle with \fIcurl_multi_cleanup(3)\fP. Be careful and please note that you \fBMUST\fP invoke separate \fIcurl_easy_cleanup(3)\fP calls on every single easy handle -- cgit v1.2.3