When we abruptly return from the write callback, the curl_easy_perform
returns a
CURL_READ_ERROR or WRITE _ERROR and as in my case i check for this
explicitly to know that i aborted the operation
Since your change still mainatins this i think it shouldnt harm existing
clients
by introducing these errors

Regards
Bharath

Daniel Stenberg wrote:

>Hey fellows!
>
>I need some input from actual users of libcurl here.
>
>I'm thinking about correcting a long-lived confusion among the error codes in
>libcurl:
>
> CURLE_WRITE_ERROR
> This error is returned *both* for errors that occurs when writing received
> data to a local file, as well as when we get problems writing data to a
> remote server. That is confusing. I want to add CURLE_SEND_ERROR for the
> latter error.
>
> CURLE_READ_ERROR
> This error is similarly returned *both* for errors when reading a local
> file, as well as when getting problems when reading network data. That is
> confusing. I want to add CURLE_RECV_ERROR for the latter error.
>
>The curl.1 (curl man page) describes these errors pretty vaguely, but
>mentions the file versions of the problems. That's why I opted to let them
>remain and move the network oriented errors to the codes.
>
>Would this be a (too) big impact on programs using libcurl?
>
>(I'm currently sitting and writing a libcurl-errors.3 man page, hence the
>focus on this right now.)
>

_______________________________________________________________

Sponsored by:
Looking for hip toys and fun scwag. There is no better place
then the good friends at ThinkGeek. http://www.ThinkGeek.com/
Received on 2002-04-09