Check out the man page for curl_multi_info_read(...)...

It would be my understanding that based on how you are doing it, in
your read function you could check for any pending message this way.
Basically you should get messages saying that an easy_handle is done,
or errored.

Perhaps keep a list of finished transfers? Have an array of struct
CURLMsg*'s as large as your number of transfers. Init all the entries
to NULL. When curl_multi_info_read returns a NON NULL you put that
value into the first NULL value you find in your array. When the
array is filled up, you're all done...and your result codes shoudl be
there.

Don't know if it is helpful, but it is one solution.

However, you're curious about a specific easy_handle, and as Daniel
mentioned, it isn't possible from the current API. So you either have
to do the work of keeping track of finished easy_handles or wait until
an API is exposed. The API exposed via curl_multi_* is different from
what you can see inside the library, so other than doing the work that
you would rather not do (keeping track of stuff), you would have to
wait for a proper API to be exposed...you can't just access the curl
functions that you can from the inside (though I wish I could
sometimes...).

On Tue, 17 Aug 2004 08:49:05 -0400, Tarendash, David
<david.tarendash_at_gs.com> wrote:
> So then comes the question, how do you know if its completed through the
> multi interface?

-- 
Casey O'Donnell
RPI STS Department - Graduate Student
http://homepage.mac.com/codonnell/
http://homepage.mac.com/codonnell/wxblogger/