HP Remote Graphics Software (RGS) Instrukcja Użytkownika Strona 112

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
Przeglądanie stron 111
you to specify timeout values that, if exceeded, will cause the RGS Receiver to take specific actions, such as
displaying a warning dialog or closing the RGS connection. The two RGS Receiver timeout properties are:
RGS Receiver warning timeout property—If this value is exceeded, the RGS Receiver displays a
network connection warning.
RGS Receiver error timeout property—If this value is exceeded, the RGS Receiver closes the
connection.
The RGS Receiver error and warning timeout properties can be set in the RGS Receiver Control Panel and are
specified in seconds. The RGS Receiver timeout properties can also be set in the rgreceiverconfig file or on a
command line—in both of these cases, the timeout properties are specified in milliseconds.
If a temporary network disruption occurs for less time than the RGS Receiver warning timeout property, the
RGS Receiver will not display a warning, and the user will experience only a brief drop in Remote Display
Window interactivity. This means, for example, that a user moving or scrolling a window might see a
momentary decrease in interactivity. If the user is not interacting with the Remote Display Window during a
temporary network disruption, the network disruption may not even be noticeable (unless dynamic content
such as video fails to update at an appropriate rate).
NOTE: In many cases, the TCP/IP network stack is able to detect and resolve network errors, such as a
transmitted packet not being acknowledged. However, if a more serious problem occurs, such as a network
cable being unplugged from the local computer, the TCP/IP stack will notify the RGS Receiver of a network
exception. In this case, the RGS connection will be closed immediately, independent of whether a network
timeout property has been exceeded.
After the RGS Receiver warning timeout property has been exceeded (two seconds, in this case), the Remote
Display Window will dim and display a warning message to the user. The dimmed window and warning
message notify the user of the potentially stale contents in the Remote Display Window. During this time, the
Remote Display Window will appear unresponsive to the user. If connectivity returns, the Remote Display
Window will return to its normal appearance and interactivity.
If the connection loss extends beyond the RGS Receiver error timeout property (30 seconds, in this case), the
Remote Display Window and the RGS Receiver connection will be closed, and the "Connection Lost!" error
dialog will be displayed.
The recommended RGS Receiver timeout strategy is to set a short warning timeout property and a longer
error timeout property. With these settings, the user is notified of potential network disruptions relatively
quickly while allowing sufficient time for the network to possibly recover. For networks with potential
disruptions greater than two seconds, a higher RGS Receiver warning timeout property may be appropriate to
lessen distraction of the user.
Experience has demonstrated that 30 seconds is a reasonable RGS Receiver error timeout property, although
some users adjust this property lower to force connections to close sooner. Higher settings, such as 60
seconds, are often impractical because they force the user to wait an inordinate amount of time before RGS
closes the connection.
RGS Sender network timeout
The RGS Sender supports the RGS Sender error timeout property, Rgsender.Network.Timeout.Error. This
property can be set only by using the rgsenderconfig file or on a command line—the RGS Sender does not
have a dialog to set this property. The RGS Sender error timeout property is independent of the RGS Receiver
timeout properties. The RGS Sender begins by using the maximum of the Rgsender.Network.Timeout.Error
property and the Rgsender.Network.Timeout.Dialog property.
When the RGS Receiver negotiates its connection to the RGS Sender, it notifies the RGS Sender of its error
timeout property. For sync pulse timeout purposes, the RGS Sender adopts the minimum of:
Rgreceiver.Network.Timeout.Error
100 Appendix B Troubleshooting
Przeglądanie stron 111
1 2 ... 107 108 109 110 111 112 113 114 115 116 117 ... 121 122

Komentarze do niniejszej Instrukcji

Brak uwag