Re: Forcing IPv6 onto existing modules

Upload it. My suggestion is IO::Socket::INET6::Force, but it's not quite right...

Sounds like the best solution, actually, might be to either merge IO::Socket::INET6 into IO::Socket::INET or just replace the latter with the former entirely if that's an option. (Especially if it's backwards-compatible...)

Comment on Re: Forcing IPv6 onto existing modules

Replies are listed 'Best First'.
Re^2: Forcing IPv6 onto existing modules by mr_mischief (Monsignor) on Dec 17, 2008 at 16:49 UTC
I think eventually replacing IO::Socket::INET with the code from IO::Socket::INET6 is actually the idea behind the latter. It had to be developed and tested separately, though. Perhaps p5p is the best place to get progress. If the one is considered robust and compatible enough to just take the place of the other, then making it the newer version of the standard module makes sense.	[reply]
Re^2: Forcing IPv6 onto existing modules by cdybedahl (Acolyte) on Dec 18, 2008 at 08:10 UTC
The problem there is that IO::Socket::INET is a core module, so replacing it needs to be done by p5p. I intend to suggest it, but any such change is not going to happen quickly.	[reply]