Great answer! This is server fault. This is not something easy.

2017-03-02 19:24 GMT-03:00 Daniel Stenberg <daniel_at_haxx.se>:

> On Thu, 2 Mar 2017, Rodrigo Zanatta Silva wrote:
>
> Lol, but you don't understand.
>>
>
> I think I do understand what you claim, but I maintain that's not how
> libcurl works.
>
> The libcurl will only get the page after it finish. So, it will take 110
>> seconds and than show all eleven lines.
>>
>
> That's incorrect. libcurl gets everything as soon as it arrives over the
> network. If you have to wait 110 seconds for the data to get sent to the
> application, that is because the server didn't send the data until then!
> (or more accurately, it wasn't read by libcurl until then)
>
> libcurl has no such delays or waiting times. libcurl does not buffer up
> things internally before it passes on the data (more than its buffer that
> it uses when recv()ing data from the kernel).
>
>
> --
>
> / daniel.haxx.se
> -----------------------------------------------------------
> Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
> Etiquette: https://curl.haxx.se/mail/etiquette.html
>

-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-03-02