Adobe 38039927 Extended User Guide - Page 269

RPCMethods class - flash download

Page 269 highlights

ADOBE FIREWORKS CS3 265 Extending Guide that could be used maliciously are not permitted in remote procedure calls (including all methods of the File object, see "Files object" on page 14 and the functions fw.launchApp and fw.findApp). The RPC server returns an invalid method error to the client if it attempts to use these methods or properties. Finally, clients can release only those objects that have been retained on their behalf. Additionally, when a client disconnects, all the server objects that have been retained on that client's behalf are released. Note: Objects are not destroyed until the client releases them or until the client that created them disconnects from the server. RPCMethods class To use remote procedure calls, Flash developers need to create an instance of a Fireworks object and thereafter manage Fireworks objects carefully to save memory. In ActionScript, you should create blocks of code where you will access the Fireworks DOM, assign a group (pool) of objects to variables, and then release those objects when you are finished. Fireworks provides the following series of memory-management functions to support ActionScript developers working with Fireworks objects. To learn more about using these functions, see "Creating autorelease blocks" on page 266 and "Accessing proxy objects" on page 267. These functions are defined in the supporting RPCMethods.as stubs file available for download from the Adobe website at www.adobe.com/go/fireworks_documentation. Note: ActionScript remote procedure calls for Fireworks are not ActionScript 1 compatible, and must be written in ActionScript 2.0 (using Flash MX 2004 or later). RPCMethods.CreateAutoReleasePool() Usage RPCMethods.CreateAutoReleasePool() Arguments None. Returns Nothing. Description Starts the auto-release block. RPCMethods.DestroyAutoReleasePool() Usage RPCMethods.DestroyAutoReleasePool() Arguments None. Returns Nothing. Description Ends the auto-release block and frees all allocated remote objects in the current auto-release block function.

  • 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
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315

ADOBE FIREWORKS CS3
Extending Guide
265
that could be used maliciously are not permitted in remote procedure calls (including all methods of the File object,
see “Files object” on page 14 and the functions
fw.launchApp
and
fw.findApp
). The RPC server returns an invalid
method error to the client if it attempts to use these methods or properties. Finally, clients can release only those
objects that have been retained on their behalf. Additionally, when a client disconnects, all the server objects that
have been retained on that client’s behalf are released.
Note:
Objects are not destroyed until the client releases them or until the client that created them disconnects from the
server.
RPCMethods class
To use remote procedure calls, Flash developers need to create an instance of a Fireworks object and thereafter
manage Fireworks objects carefully to save memory. In ActionScript, you should create blocks of code where you
will access the Fireworks DOM, assign a group (
pool
) of objects to variables, and then release those objects when
you are finished. Fireworks provides the following series of memory-management functions to support Action-
Script developers working with Fireworks objects. To learn more about using these functions, see “Creating auto-
release blocks” on page 266 and “Accessing proxy objects” on page 267. These functions are defined in the supporting
RPCMethods.as stubs file available for download from the Adobe website at
www.adobe.com/go/fireworks_documentation
.
Note:
ActionScript remote procedure calls for Fireworks are not ActionScript 1 compatible, and must be written in
ActionScript 2.0 (using Flash MX 2004 or later).
RPCMethods.CreateAutoReleasePool()
Usage
RPCMethods.CreateAutoReleasePool()
Arguments
None.
Returns
Nothing.
Description
Starts the auto-release block.
RPCMethods.DestroyAutoReleasePool()
Usage
RPCMethods.DestroyAutoReleasePool()
Arguments
None.
Returns
Nothing.
Description
Ends the auto-release block and frees all allocated remote objects in the current auto-release block function.