> "Solutions" that only shift the problem into less visited area or drop the > problem to users is not a way to go. > > Quoting RFC 6724: > > > Well-behaved applications SHOULD NOT simply use the first address > > returned from an API such as getaddrinfo() and then give up if it > > fails. For many applications, it is appropriate to iterate through > > the list of addresses returned from getaddrinfo() until a working > > address is found. *For other applications, it might be appropriate to > > try multiple addresses in parallel (e.g., with some small delay in > > between) and use the first one to succeed.*
That is likely why MS introduced WSAConnectByList function, which returns a connection for the first available hosts based on IP address list (both IPv4 and IPv6 addresses). (https://msdn.microsoft.com/en-us/library/windows/desktop/ms741554(v=vs.85).aspx) Unfortunately, this function available in server OS starting with Win2003 but is only available on client OS as of Win8.1 (the page awkwardly refers to Vista support -- which would imply Win7+) Sean ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
