On Wed, Apr 27, 2016 at 04:48:53PM +0200, Dimitry Sibiryakov wrote:
> 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.*
Yes, sure, it's not really forbidden. But there is quite a difference
between "for many application, it is appropriate" and "for other
applications, it might be appropriate". I don't really see Firebird
belonging into the latter group, that would be rather domain of clients
opening short connections to many different hosts.
If we really were to go this way, I would at least suggest to use a
delay between the attempts as indicated in the RFC, preferrably
at least something similar to minimum TCP retransmit timeout (200 ms on
Linux). The initial retransmit timeout would be more logical choice but
that, in fact, is one second.
Michal Kubecek
------------------------------------------------------------------------------
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
