Hi Logan On 5/31/07, Buesching, Logan J <[EMAIL PROTECTED]> wrote:
I have an attached patch file that I am about to commit, but once again as I am pretty new to the documentation team, I wanted to know if anyone had any feedback before I did so.
I only did a cursory look, seems fine overall, but here are a few notes: Add markup (<constant />) around the constants (CURLOPT_RETURNTRANSFER & CURLM_OK) curl_multi_info_read: + <para> + Ask the multi handle if there are any messages/informationals from the individual transfers. + Messages may include informationals such as an error code from the transfer or just the fact + that a transfer is completed. + + Repeated calls to this function will return a new result each time, until a &false; is returned + as a signal that there is no more to get at this point. The integer pointed to with + <parameter>msgs_in_queue</parameter> will contain the number of remaining messages after this + function was called. + </para> All that whitespace in between will be ignored. The <para /> element works pretty much the same way as the <p /> element in x/html, so feel free to wrap each paragraph with <para />. 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? The while($running) sleep(1); example also seems weird, are you absolutely sure it work as expected? -Hannes
