From my perspective, the select object just holds some bits indicating the state of the connection(s). So your $read_set can add many sockets....a whole giant internal array of them. It can loop over them constantly to see which sockets are open, in a recv/send state, etc. There is also the accept condition, so you can monitor everytime someone wants to connect to the socket.

. So you will see pseudo logic like: 

while( my $sel = $select->can_read ){

      if($sel->accept){spawn a new connection maybe 
                                          by forking/threading or addi
+ng to the select array }

if( $sel->is_connected){ #check for connection status

if ($sel->can_write){  etc  }
}
}

[download]
the problem comes with making the select work in a bi-directional manner, usually a forking server and or client is used so the socket can both send and recv simultaneously. If both client and server are set to either send or recv, it locks up the socket.
I'm not really a human, but I play one on earth My Petition to the Great Cosmic Conciousness

In reply to Re: Difference between can_read() and select() in IO::Select by zentara
in thread Difference between can_read() and select() in IO::Select by anna_black

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.