I have a server based on the following IO::Select example code with non-blocking clients. It does not recognise when the connection is closed by the other end... the handle still is still opened() and not in error() and the select->has_exception list is empty. On the other hand the select->can_read in this example goes into a tight loop. How do I fix this whilst still using non blocking IO (and is using getlines ok with NIO?)
$server = new IO::Socket::INET(Listen => 1, LocalPort => 8080) || +die "$!"; $sel = new IO::Select( $lsn ); while(@ready = $sel->can_read) { foreach $fh (@ready) { if($fh == $server) { # Create a new socket $new = $lsn->accept; $new->blocking(0); $sel->add($new); } else { # Process socket print "ERROR ",$fh->error," OPENED ",$fh->opened,"\n"; print $fh -> getlines; }

In reply to IO::Select->can_read isn't recognising closed INET connections by Anonymous Monk

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.