Using Remote Graphics Software

two seconds (two-thousand milliseconds). The default error timeout is thirty seconds (thirty-thousand milliseconds).

In a practical example, if a temporary network disruption occurs for less than two seconds, the Receiver does not display a user notification and the user only experiences a brief drop in Remote Display Window interactivity. This means that, for a user moving or scrolling a window, the window will appear unresponsive or hung. If no interaction with the display occurred while the network stalls, the event is usually not even notable unless dynamic content such as video fails to update in a reasonable amount of time.

If the disruption continues for greater than two seconds, then the Remote Display Window dims and a warning appears. During this time the Remote Display Window appears unresponsive to users. If connectivity returns, then the Remote Display Window returns to its normal appearance and interactivity. A full loss of connection beyond the error timeout results in closure of the Remote Display Window and display of the "Connection Lost" error dialog as previously described.

Receiver properties are fully settable from the Receiver properties resource file or command line. The default value for the Receiver property, Rgreceiver.Network.Timeout.Warning, is 2,000 milliseconds (two seconds). This value works well for most installations. For networks with less stable connectivity and disruptions greater than two seconds, higher warning timeout values will lessen the appearance of network warning as a nuisance to user productivity.

The recommended default value for the Receiver property, Rgreceiver.Network.Timeout.Error, is 30,000 milliseconds (thirty seconds). In practice, this works well, although some users adjust this value lower to force connections to close sooner. Higher settings of one minute (60,000 milliseconds or

109