The MultiConnectionConfig type exposes the following events.

Events

 Public

 Protected
 Instance

 Static
 Declared

 Inherited
 XNA Framework Only

 .NET Compact Framework Only

 MemberDescription
ConnectionEstablishedEvent
Fired whenever any connection succeeds, including the very first one. After a roughFailover, the first server to which a successful connection is made will become the primary, and any active queries will be resubmitted to it.
ReconnectFailedEvent
Fired whenever an attempt to make a connection fails. Note that this is, by definition, not the primary connection, because it was already known to be in a failed state. That is, a SmoothFailoverEvent or SmoothFailoverEvent was previously fired call if this was the primary connection, or a SecondaryConnectionLostEvent if this was a successful secondary connection. Or this server was never connected to before.
RoughFailoverEvent
Fired when the current server has failed and there is no other server ready to fail over to. This will be called just before the process of resubmitting all the queries to the new primary server. If you do not want the queries to be resubmitted, you can close all the queries before returning from this call.
SecondaryConnectionLostEvent
Fired whenever one of the secondary connections has been lost. Since the primary connection is still working fine this is just for information purposes. Nothing will happen to any ongoing queries.
SmoothFailoverEvent
Fired when the current server has failed, but there is already another server ready to fail over to. The system is already trying to connect to other servers in the list. However, it will not resubmit any queries until this call has completed. If you do not want the queries to be resubmitted, you can close all the queries before returning from this call.

See Also