thank for your answer,

yes I use persistent connections (files are on the same server), but in fact
Im studying the problem, and then I will choose between issues. And Im
looking for the most adapted issue to loose less time as possible. And about
pipelining, Im not sure to understand how it works : i read that i could
send many requests and then get the results. Does it mean there is only one
http request sent ? So if I have 40ms latency, then the request will take
40ms + data sending time ? or 40 ms * the number of requests i did ?

On 5/8/07, Daniel Stenberg <daniel_at_haxx.se> wrote:
>
> On Tue, 8 May 2007, Nicolas REMIA wrote:
>
> > Im using libcurl in that way: i have 20 threads, and each thread manages
> an
> > easy curl handle. Then, threads fight to obtain an url (in a shared
> pool) to
> > download. Most of my requests are ranged requests.
>
> But you do try to make the same handles transfer from the same host again,
> right? I mean so that you can use persistent connections as far as
> possible.
>
> > Should i manage myself to ask for several objects in one request using a
> > ranged request like => 0-42,142-242,330-369. It means a local pool for
> each
> > thread, waiting for a minimum number of files to download. Or should i
> use
> > http pipelining ? My main problem is to dodge the latency, so make the
> less
> > number of requests.
>
> I would assume that you can do both and gain performance for both steps.
>
> --
> Commercial curl and libcurl Technical Support: http://haxx.se/curl.html
>
Received on 2007-05-08