On Tuesday, June 11 2002, Daniel Stenberg wrote:

> [I'm cc'ing this to the libcurl mailing list as this definitely is a
library
> issue. Please take follow-ups there.]

Doh! <smacks palm on forehead> Sorry for the mispost.

> You need to make one of the callbacks return an appropriate return code
to
> make curl stop. There is no other way.

Thanks for the reply Daniel.

On ftp send, I wasn't using the read callback, but its easy enough to switch
over to it. Am I correct to assume the read callback won't get called util
a connection has been established? Will the read callback ever get called
if there is some problem connecting? I guess I'm at the mercy of the system
timeouts as far as waiting for a connection or an error to occur (I'm using
a worker thread to send files to prevent blocking).

Have you given any though to establishing some sort of communication state
notification callback? (I see in the docs that the progress meter is going
away at some point.) I'm suggesting something that reports pre-defined
connection progress states, if the caller asks to be informed. That way,
the callback could tell curl_easy_perform to abort during one of these
notifications.

Thanks again for the help.

tom.

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
Received on 2002-06-11