If you were using something like POE::Component::Client::HTTP (see these recipes), I would recommend starting a polite number of parallel requests, perhaps 10 or 20, and then firing off a new request for each response that arrives. This is a handy way to limit parallelism without a lot of bookkeeping.

You may still be able to do this. It depends whether you can join() on "the next thread to finish". For every thread that joins, start another with the next request. Exit when you've run out of @addresses and @threads.

--
Rocco Caputo - http://poe.perl.org/ - irc://irc.perl.org/poe

In reply to Re: Threaded Web requests by rcaputo
in thread Threaded Web requests by schnibitz

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.