in reply to Re^2: HTTP Requests and Threading
in thread HTTP Requests and Threading

Your threads run concurrently and will take different times to complete depending upon a bunch of factors -- the remote server's workload; distance and latency of the link between your machine and those servers; the size of the page returned; etc. -- so the order in which they finish will be unrelated to the order that you start them. That is normal.

If you want to control the order of the output, you will need to accumulate the results and arrange to output them in your desired order.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

Replies are listed 'Best First'.
Re^4: HTTP Requests and Threading
by carlriz (Beadle) on Mar 07, 2014 at 16:10 UTC

    That makes sense.

[reply]

In Section Seekers of Perl Wisdom