Internally, IO::Socket passes around a seperate $sock for each connection. Well, I tested my change by taking the nonblock example from the Perl Cookbook, making it use persistent LISTEN sockets, and then adding the following code in the request handling sub. 
        print "GOT LEN " . length($client->peername) . "\n";
        my($port, $ipaddr) = sockaddr_in($client->peername);
        print "GOT PORT $port\n";

[download]
I connected from multiple hosts, getting the right port each time, then restarted the listener, connected again from multiple hosts and still got the expected results from my inserted block of code.

In reply to Re^2: IO::Socket doing getpeername twice on every send? by cazz
in thread IO::Socket doing getpeername twice on every send? by cazz

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.