On 2006-06-01, Daniel Stenberg wrote:
> I could agree to most of what you said until this point. Having
> curl_easy_perform() return before the entire request is complete would
> introduce a huge can of worms as that is not how curl_easy_perform()
> behaves today. I would say that it should continue spitting out parts to
> the callback as long as the stream is alive. It would of course also
> require some sort of separating info/callback to the app when one part is
> completely transfered.

Yeah, it is different...

> If you'd want to get back "control" and do something else before allowing
> another multipart, you'd instead use the multi interface as it would then
> provide such a feature "automatically".

Maybe a new call could be added to syncronously get one part?

I'll get back to you when/if I get back to this stuff!

Thanks for your time

Regards,
Daniel
Received on 2006-06-02