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

detected by, the Receiver

Page 120 highlights

Figure 6-22 shows the sequence of events commencing when sync pulses cease being detected by the Receiver. Figure 6-22 Receiver timeout sequence • TCP/IP stack may detect & resolve problems. • Network disruption may not be noticeable. • Serious network problems may cause the RGS connection to close. 2 0 seconds sync pulses stop being detected by the Receiver network warning timeout property exceeded 30 seconds network error timeout property exceeded time After the Receiver warning timeout property has been exceeded (two seconds, in this case), the Receiver 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 Receiver error timeout property (30 seconds, in this case), the Remote Display Window and the Receiver connection will be closed, and the "Connection Lost!" error dialog will be displayed. The recommended 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 Receiver warning timeout property may be appropriate to lessen distraction of the user. Experience has demonstrated that 30 seconds is a reasonable 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. Advanced capabilities 120

  • 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 120
Figure 6-22 shows the sequence of events commencing when sync pulses cease being detected by the Receiver.
Figure 6-22
Receiver timeout sequence
After the Receiver warning timeout property has been exceeded (two seconds, in this case), the Receiver 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 Receiver error timeout property (30 seconds, in this case), the Remote
Display Window and the Receiver connection will be closed, and the "Connection Lost!" error dialog will be
displayed.
The recommended 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 Receiver warning timeout property may be appropriate to lessen distraction of the user.
Experience has demonstrated that 30 seconds is a reasonable 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.
sync pulses
stop being
detected by
the Receiver
network warning
timeout property
exceeded
network error
timeout property
exceeded
TCP/IP stack may detect &
resolve problems.
Network disruption may not
be noticeable.
Serious network problems
may cause the RGS
connection to close.
time
0
2
seconds
30
seconds