HP Xw460c Remote Graphics Software 4.2.0 User Guide - Page 115

Display Window.

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 115 highlights

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

  • 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
Using Remote Graphics Software
107
•
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.