Hello, Daniel.

Friday, November 16, 2007, you wrote:

>> Are you intending that this curl_easy_pause() should be called outside
>> read/write callback?

> Yes, or from within it. I wouldn't restrict it to either way.

Oh, then I was falsely understand that you want to restrict
curl_easy_pause() to be called outside callbacks, to prevent libcurl
from reading data from connection and storing this data.

Then, on my mind, there is no serious obstacles to do it via
curl_easy_pause() instead of return code. Especially if it ease
implementation of non-blocking. My main idea is to allow blocking
inside the callback.
It is just my thoughts. The return code is still good way for me too.

> It made me think about allowing a write callback to deal with a part
> of the buffer and then block, instead of just blocking everything...
> But on second thoughts I think we can ignore that for simplicity.

Actually it is a good idea. But on my mind can be ignored for
simplicity too.

So, does such functionality can appear in some next version?
Thanks.

--
Best regards,
  Dmitriy Sergeyev
C++ Developer of ISS Art, Ltd., Omsk, Russia.
http://issart.com