Re^2: What should be default for Net::Server

in reply to Re: What should be default for Net::Server - IPv4, IPv6 or IPv*
in thread What should be default for Net::Server - IPv4, IPv6 or IPv*

The only problem with compatibility - is compatibility with which version.

IPv4 as default is compatible with all official versions including 0.99.

IPv* as default is compatible with the unofficial (but head for 9 months) version 0.99.6.1

my @a=qw(random brilliant braindead); print $a[rand(@a)];

Comment on Re^2: What should be default for Net::Server - IPv4, IPv6 or IPv*
Re^3: What should be default for Net::Server - IPv4, IPv6 or IPv* by Anonymous Monk on Jun 02, 2012 at 00:42 UTC
but IP* would work for anyone who has ipv4 already set... i.e., it doesn't break anything. It just adds ipv6 to the mix. I basically ran across this because our company is making massive moves to make sure everything easily supports ipv4, ipv4/ipv6, and ipv6 modes of operation.	[reply]
Re^3: What should be default for Net::Server - IPv4, IPv6 or IPv* by mbethke (Hermit) on Jun 02, 2012 at 02:41 UTC
Compatibility with what most people use. People who use unofficial HEADs should know what they are doing and particularly be aware that defaults may change from one version to the other---obviously they've had this experience at least once. Those who just run "aptitude upgrade" or equivalents to be fed the latest stable version are less likely to pay attention to these things and just expect their applications to behave the same. You could just `warn()` people who haven't explicitly set a protocol family about impending changes in the default for a while and then switch it.	[reply]


Perl: the Markov chain saw
	PerlMonks

Re^2: What should be default for Net::Server - IPv4, IPv6 or IPv*

The best material for plates (tableware) is: