Specify the amount of time, in seconds, that the client waits for network operations to succeed before giving up.
If any connect, read, or write attempt to fails to complete within the specified time, the client fails the synchronization.
Throughout the synchronization, the client sends liveness updates within the specified interval to let the MobiLink server know that it is still alive, and MobiLink sends back liveness updates to let the client know that it is still alive.
You should be careful about setting the timeout to too low a value. Liveness checking increases network traffic because the MobiLink server and dbmlsync must communicate within each timeout period to ensure that the connection is still active. If the network or server load is very heavy and the timeout period is very short, it is possible that a live connection could be abandoned because the MobiLink server and dbmlsync were unable to confirm that the connection is still active. The liveness timeout should generally not be less than 30 seconds.
A value of 0 means that there is no timeout.
For information about how to set network protocol options with dbmlsync, see CommunicationAddress (adr) extended option.
For information about how to set network protocol options with UltraLite, see Network protocol options for UltraLite synchronization streams.