HP Z620 HP Remote Graphics Software 5.4.7 - Page 192

shows the sequence chart for this.

Page 192 highlights

used to permanently enable or disable global image updates in the Receiver. The default value is 1- global image updates can be configured by the user. Rgreceiver.IsGlobalImageUpdateEnabled=bool (0) Rgreceiver.IsGlobalImageUpdateEnabled.IsMutable=bool (1) If set to 1, the Receiver updates the area of the screen with the extents of all the areas of the screen that have changed. If set to 0, the Receiver limits updates of the screen to just the areas that have changed, using individual update rectangles. If image updates in the Remote Display Window show image tearing, setting the value to 1 (enabling global image updates) may reduce the tearing. Tearing usually occurs on large images that are updated quite frequently, such as a 3D object being rotated in a large window. Setting the property value to 0 (disabling global image updates) is usually best for large Remote Display Windows (5120 x 1024 resolution) that display mostly text based applications. The default value is 0-global image updates are disabled. NOTE: The following property was added in the RGS 5.1.3 release to enable RGS performance optimization in high-latency network environments. Rgreceiver.MaxImageUpdateRequests=int (4) Rgreceiver.MaxImageUpdateRequests.IsMutable=bool (1) This property controls the maximum number of outstanding image update requests between the RGS Receiver (requestor) and the RGS Sender (responder). Prior to RGS 5.1.3, the number of outstanding image update requests was preset to 1. This meant that the Receiver, after issuing an image update request, would wait for the image update response to be completed before issuing another request. Figure 8-5 Prior to RGS 5.1.3, only one image update would be in-process at any time on page 176 shows the sequence chart for this. Figure 8-5 Prior to RGS 5.1.3, only one image update would be in-process at any time The Rgreceiver.MaxImageUpdateRequests property was added to enable performance optimization in high-latency network environments. For example, setting this property to 2 will allow the Receiver to issue a second image update request to the Sender prior to receiving the previous image update response. This allows the Sender and Receiver to operate more in parallel-but at the potential expense of increased network bandwidth consumption. 176 Chapter 8 RGS properties

  • 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
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

used to permanently enable or disable global image updates in the Receiver. The default value is 1—
global image updates can be configured by the user.
Rgreceiver.IsGlobalImageUpdateEnabled
=bool
0
Rgreceiver.IsGlobalImageUpdateEnabled.IsMutable
=bool
1
If set to 1, the Receiver updates the area of the screen with the
extents
of all the areas of the screen
that have changed. If set to 0, the Receiver limits updates of the screen to just the areas that have
changed, using individual update rectangles.
If image updates in the Remote Display Window show image tearing, setting the value to 1 (enabling
global image updates) may reduce the tearing. Tearing usually occurs on large images that are
updated quite frequently, such as a 3D object being rotated in a large window. Setting the property
value to 0 (disabling global image updates) is usually best for large Remote Display Windows (5120 x
1024 resolution) that display mostly text based applications. The default value is 0—global image
updates are disabled.
NOTE:
The following property was added in the RGS 5.1.3 release to enable RGS performance
optimization in high-latency network environments.
Rgreceiver.MaxImageUpdateRequests=int
4
Rgreceiver.MaxImageUpdateRequests.IsMutable=bool
1
This property controls the maximum number of outstanding image update requests between the RGS
Receiver (requestor) and the RGS Sender (responder). Prior to RGS 5.1.3, the number of outstanding
image update requests was preset to 1. This meant that the Receiver, after issuing an image update
request, would wait for the image update response to be completed before issuing another request.
Figure
8
-
5
Prior to RGS 5.1.3, only one image update would be in-process at any time
on page
176
shows the sequence chart for this.
Figure 8-5
Prior to RGS 5.1.3, only one image update would be in-process at any time
The
Rgreceiver.MaxImageUpdateRequests
property was added to enable performance
optimization in high-latency network environments. For example, setting this property to 2 will allow the
Receiver to issue a second image update request to the Sender prior to receiving the previous image
update response. This allows the Sender and Receiver to operate more in parallel—but at the potential
expense of increased network bandwidth consumption.
176
Chapter 8
RGS properties