Background: I've been a Linux user forever. Be default, both Windows and Linux use IPv6 for connecting to a host's address when it is available (in a dual-stack environment, at least). It appears that OS X Mountain Lion does some sort of latency checking and will regularly flip back and forth between IPv4 and IPv6 for address resolution of the same host.
In theory this should be a fine approach, but I've seen some weirdness with the combination of Chrome, SPDY, and opening a lot of connections at the same time. Does anyone know of a hidden flag to force it to use IPv6 when available for a host?
Some quick Google searching yields limited coverage and no success:
»
stackoverflow.com/questi ··· ain-lion