In the DA collective there is a function called "Failback". The function is described as:
<< When the collective member which the client application was connected to becomes unavailable, the client connection starts monitoring when the member becomes available again. When it happens, it should switch back to that member.
This is done by the client application (it is not anyhow forced by the server) and it is done to:
Honor connection priorities
Restore connection distribution (if member priorities are equal). >>
The problem with this is that if primary has been down for a while the buffer needs to fill the gap. The client can not access real time data until the buffer is backfilled.
I would like the failback function to be optional. In that way the clients can have real time data continiously.
