I'm playing aroudn with IO::Socket and IO::Select. One problem I've encounted is that IO::Select will return a list of socket connections (filehandles), but you will not know which socket is which.

Is it possible to use these as hash keys? For example: 

@readable_handles=$selectobj->can_read(0.1);
foreach my $socket (@readable_handles) {
    $sockethash{$socket}->{readable}=1;
}
# other places in the program can identify which 
# connection is being discussed by using the connection
# handle as a hash key

[download]
(I've tried it, and -w and use strict don't complain, but my script isn't working overall...I can't tell if this is due to my lack of sockets comprehension, or this trick.)

If this doesn't work, is there an easy way to identify what socket you are dealing with?

In reply to Sockets/filehandles as hash key? by swiftone

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.