Hi Armel and Daniel,

  On 12/17/06, Daniel Stenberg <daniel_at_haxx.se> wrote:
    On Fri, 15 Dec 2006, Armel Asselin wrote:

> - we could have a CURLOPT_CANCEL which could be set to 1 while a CURL easy
> handle is running, in this case, the current request would get ended as fast
> as possible. we could have several code here such as: 'cancel nicely' (what
> we are trying to do), 'cancel hardly' (would just end marking connection
> invalid, doing nothing intelligent but ultra-fast).

    Before even considering adding this option and the various ways of dealing
    with them, I think we should consider if there's any interest from users in
    it. Remember that you are the first person who brought this issue up, so this
    is not a big issue to people.

  curl-loader has added a very premature support for ftp urls to be used for traffic
  generation, loading, testing, etc (still, not well tested with several pending issues).
  Indeed, the options of "cancel hardly" and 'cancel nicely' could be helpful in storming and smooth modes, when dealing with multi-interface and FTP.

now that I have a bit more experience with my own tool and the 'hard cancellation' (coded with a CURLE_CANCELED error code passed to curl_ftp_done, currently). this way seems rather acceptable, even performance-wise.
what I would like is then to progress first on this, having something official and working.
this thread is still interesting because we viewed the main problems i think and we could keep in archive for later improvements.

so, from my point of view adding a simple test of the multi state wrt COMPLETED and setting some error code would OK for that purpose (which one? there is nothing very appealing in the list).

Armel
Received on 2006-12-22