On 6/1/07, Buesching, Logan J <[EMAIL PROTECTED]> wrote:
> curl_multi_init:
> + <para>
> + Returns a cURL on handle on success, &false; on failure.
> + </para>
> + <note>
> + <para>
> + This only returns errors regarding the whole multi stack. There
> might still have
> + occurred problems on individual transfers even when this function
> returns CURLM_OK.
> + </para>
> + </note>
>
> This is confusing, it returns a resource on success and CURLM_OK?
This note was actually suppose to be documented in the curl_multi_exec()
function, not the init() function. Good catch!
> The while($running) sleep(1); example also seems weird, are you
> absolutely sure it work as expected?
>
I must have been really tired.... looking back on that now makes me
scratch my head too.... I think I mis-read some documentation thinking
that the running flag wasn't exactly what it is. I removed that part
from the examples as I wanted to create a simple example and leave user
notes for some more advanced things, such as for what the $running flag
is used for.
Thank you Hannes for the quick pass over the document. I just committed
the changes so the cURL library should be fully documented.
Awesome!
But it isn't _fully_ documented yet (*hint* *hint*) ;)
There are gazillion constants that need one-line-description on what
they do and resorting them wouldn't hurt either (error constants, info
constants, ftp...)
-Hannes
