On Mon, 3 Mar 2008, Pierre Ynard wrote:

> Currently, the PROGRESSFUNCTION callback can be used in place of a possible
> INTERRUPTFUNCTION with a latency of one second, but only when the transfer
> state has been established. And, as a developper, I would still be reluctant
> to divert it from its purpose.

Well, it would perhaps make sense to also make the progress callback get
called when libcurl has figured out a function was aborted due to a signal. It
would also be a very API- and ABI-friendly change.

Wouldn't that fill you need? And to clarify: the progress callback can be
called before the transfer begins, as it is used to indicate progress of the
operation and that covers the entire process.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html