It seems that I'm making assumptions about the functionality of IO::Socket::INET that just aren't true. For example, you can't really reconnect unless you jump through a bunch of hoops. The $socket->connect() method, for example, is no more robust than the internal one. You need to resolve your addresses first using gethostbyaddr, which is inconvenient, to say the least. So it can be done, but the cost is too high to make it practical.

Maybe this will be fixed in an upcoming release.

In the interim, recreating the socket doesn't seem like such a big deal after all. It will certainly work.

In reply to Re^3: IO::Socket to me. . . or why won't you stay? by tadman
in thread IO::Socket to me. . . or why won't you stay? by Hero Zzyzzx

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.