--As of September 6, 2010 2:58:36 PM +0100, Paul LeoNerd Evans is alleged
to have said:
In order to provide an easy transition period, I'd also support
additional IO::Socket::INET options where they still make sense; e.g.
accepting {Local/Peer}Port as a synonym for {Local/Peer}Service. The
upshot here ought to be that you can simply
sed -i s/IO::Socket::INET/IO::Socket::YourNameHere/
and suddenly your code will JustWork on IPv6 in a good >90% of cases.
Can anyone suggest me a better module name for this?
--As for the rest, it is mine.
Honestly, the name I'd want on that module is IO::Socket::INET. Fix the
whole problem, instead of just being the new best choice. (For everyone
who bothers to notice, and upgrade.)
Daniel T. Staal
---------------------------------------------------------------
This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------
