One thing I haven't yet seen mentioned elsewhere in this thread is use of IO::Socket::IP, which can be used as a drop-in replacement for the more outdated IO::Socket::INET class. The newer version supports IPv6, so the only real reason to use the IPv4-only outdated version is when you're using a version of Perl before 5.20 (or need to maintain compatibility) and are unable to use the CPAN version of IO::Socket::IP.
Even if you don't have a current need to support IPv6, you make future expansion harder, and in today's Internet where IPv6 is (finally!) becoming more common, it's getting far harder to ignore. There's often little reason to avoid use of IO::Socket::IP since it supports both IPv4 and IPv6, and is also usable with the family-neutral functions provided by the Socket library (such as Socket::getaddrinfo.)
Consider if there's a good reason you want to write non-portable code that assumes IPv4 will be (exclusively) used everywhere your code will be.
In reply to Re: Bidirectional Client/Server - to fork or not to fork?
by Apero
in thread Bidirectional Client/Server - to fork or not to fork?
by ljamison
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |