According to the document, the callback for CURLOPT_READFUNCTION should
not "pre-maturely" return 0 which will let the server hang waiting for the
rest of the data that won't come. Instead, after 7.12.1, the callback may
return CURL_READFUNC_ABORT to stop the current operation. However, the
value of CURL_READFUNC_ABORT is 42, a number that cannot distinguish from
a normal return. How can it signal to stop the operation? What then is the
correct way to stop?

Bill
Received on 2005-06-28