Using Remote Graphics Software
∙a network cable can be pulled (done often during testing) from its port
∙other failures are possible, too.
In some network scenarios, a disruption is transient while in other networks the connectivity loss is more permanent. For example, a network cable can be accidentally pulled and then plugged in again resulting in the network being restored. If a network disruption is temporary, a network stack may wait and attempt to recover connectivity before giving up and fully disconnecting. This is what the TCP layer of the TCP/IP network stack automatically does. If a temporary network disruption occurs, the network stack often detects the condition and continues to retry, subject to the timeout parameters set in the TCP/IP network stack. However, during these intervals of network inactivity, it is often important that the user receive notification of a potential network connectivity loss, especially if important decisions depend upon the temporal accuracy of the data presented to the user in the Remote Display Window.
If connectivity is restored after a disruption, the RGS Receiver should continue to receive updates and operate normally. In many cases, the user should experience little or no inconvenience if connectivity is restored in a short amount of time.
However, if network connectivity loss persists, then a connection decision is required to either wait, retry, or permanently close a connection. If the error timeout expires, the RGS Receiver and Sender will fully close their connections and a new connection must be initiated by the Receiver to restore connectivity.
107