Erik LaBianca wrote:

> = m. Th = wrote:
>
>
>> Note that this can be done also on Windows (when the remote shadows will
>> be implemented) and is blazingly fast (at 1Gbps is transparent) and,
>> also, rock solid at crash tests (details available on request - remote
>> shadows on Windows were tested on an experimental SS RC5 build for
>> Windows). Perhaps a better approach is to have on the client the
>> redirection engine. (On both servers the fbserver is running) Ie. in
>> TIBODatabase.OnError do something like:
>>
> snip
>
>> IMHO, this is much more simpler, faster, platform independent and
>> doesn't introduce the side effects of changing the IP in the LAN.
>>
>> hth,
>>
>> m. th.
>>
>
> I personally wouldn't be real comfortable pushing the failover logic to
> the client. What happens when two clients notice the master is dead and
> try to initiate the failover at the same time?

No problem. The second one will see that the shadow is already activated
(trying to connect) and gracefully changes the connection string.

> There's no reason you
> couldn't have a 'special' client running on the slave server doing what
> you suggest though.
>

Of course. But in this case how you will inform the other clients of the
change?

hth,

m. th.