e of IO::Socket::IP, which can be used as a drop-in replacement for the more outdated IO::Socket::INET class.
Is there a good reason why this is a new module (name) rather than integrated transparently into the IO::Socket::* hierachy?
In reply to Re^2: Bidirectional Client/Server - to fork or not to fork?
by BrowserUk
in thread Bidirectional Client/Server - to fork or not to fork?
by ljamison
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |