If the only thing you do with the IO::Socket::INET and read and write from it, you won't have any problem since the object is not used at all for that (just the file handle on which its built). 

use strict;
use warnings;
use threads;
use IO::Socket::INET qw( );
use constant SHUT_WR => 1;

my $sock = IO::Socket::INET->new(
   Proto    => 'tcp',
   PeerAddr => $ARGV[0] // 'localhost:echo',
)
   or die $!;

async {
   print while <$sock>;
};

async {
   print($sock "abc\n");
   sleep(3);
   print($sock "def\n");
   shutdown($sock, SHUT_WR);
};

$_->join for threads->list;

[download]

I don't know for IO::Socket::SSL.

Update: Added default argument.

In reply to Re: Can I/O operations on the same IO::Socket be executed in different threads? by ikegami
in thread Can I/O operations on the same IO::Socket be executed in different threads? 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.