> Right, there is no way to try to simultaneously connect using ipv4 > and ipv6, apparently.
Ah, I see what you meant. No, this cannot work - what if you get positive ACKs on both protocols? > Also, the problem with setting the registry TcpConnectMaxRetries > registry entry is that it also affects retries wen no ACK is > received. This is probably something one doesn't want to mess with. Indeed. They were wrong to overload this setting. > Okay, so do we want to bug MS about this? If you think it helps, go ahead! This has been in the system for so long that they are unlikely to change it. Yet, as IPv6 deployment progresses, this case will occur more and more often (until eventually all services are dual-stacked - in which case the only effect will be that you wait 2 seconds if the service is really not available; 1s delay per protocol). If the default retry counter can't be changed, I'd suggest that they provide a socket option. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com