HP ProLiant xw2x220c Remote Graphics Software 5.3.0 User Guide - Page 119

Receiver network timeouts, Receiver Control Panel

Page 119 highlights

Receiver network timeouts RGS provides two user-settable Receiver timeout properties to allow you to optimize RGS for your particular network conditions (such as low-bandwidth or high-latency conditions). These properties allow 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 Receiver timeout properties are: • Receiver warning timeout property-If this value is exceeded, the Receiver displays a network connection warning. • Receiver error timeout property-If this value is exceeded, the Receiver closes the connection. The Receiver error and warning timeout properties can be set in the Receiver Control Panel (see Figure 6-21), and are specified in seconds. The 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. Figure 6-21 shows the default Receiver timeout periods and the corresponding timeout properties. Figure 6-21 Receiver Control Panel Rgreceiver.Network.Timeout.Error=30000 Rgreceiver.Network.Timeout.Warning=2000 Rgreceiver.Network.Timeout.Dialog=15000 If a temporary network disruption occurs for less time than the Receiver warning timeout property, the 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. Advanced capabilities 119

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196

Advanced capabilities 119
Receiver network timeouts
RGS provides two user-settable Receiver timeout properties to allow you to optimize RGS for your particular
network conditions (such as low-bandwidth or high-latency conditions). These properties allow 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 Receiver timeout properties are:
Receiver warning timeout property
—If this value is exceeded, the Receiver displays a network connection
warning.
Receiver error timeout property
—If this value is exceeded, the Receiver closes the connection.
The Receiver error and warning timeout properties can be set in the Receiver Control Panel (see Figure 6-21), and
are specified in seconds. The 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. Figure 6-21 shows the
default Receiver timeout periods and the corresponding timeout properties.
Figure 6-21
Receiver Control Panel
If a temporary network disruption occurs for less time than the Receiver warning timeout property, the 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.
Rgreceiver.Network.Timeout.Error=30000
Rgreceiver.Network.Timeout.Warning=2000
Rgreceiver.Network.Timeout.Dialog=15000