MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Instrukcja Użytkownika Pobierz pdf (Strona 49)

Configuring Flash Communication Server 49

• The <StorageDir> tag inside the <SharedObjManager> tag indicates the directory where

shared objects should be stored. The default is a directory named Sharedobjects in the

application’s directory. The default is used if no directory is specified. When specifying a

directory, use an absolute path. (For more information about shared objects, see Developing

Communication Applications.)

• <Client> is a container for the <Bandwidth>, <BandwidthCap>, and <HTTPTunnel> tags.

• <Bandwidth> is a container for two tags that control the amount of bandwidth to use for

upstream (client-to-server) and downstream (server-to-client) data traffic. By default, this tag

includes an

override parameter set to “yes”, which allows both of its subtags to be

overridden.

• <ServerToClient> specifies the maximum speed at which the server sends data to the client.

The default is 250K (250,000 bytes per second) per client.

• <ClientToServer> specifies the maximum speed at which the client sends data to the server.

The default is 250K (250,000 bytes per second) per client.

• <BandwidthCap> is a container for two tags that specify the maximum values that can be used

when remotely editing the preceding <ServerToClient> and <ClientToServer> tags inside

the

<Bandwidth> tag. By default, this tag includes an override parameter set to “no”. For

more information about editing server configuration remotely, see the Macromedia Flash

Support Center at www.macromedia.com/support/flash/.

• <ServerToClient> specifies the maximum speed that can be configured remotely for sending

data to the client. The default is 10 MB (10,000,000 bytes per second).

• <ClientToServer> specifies the maximum speed that can be configured remotely for sending

data to the server. The default is 10 MB (10,000,000 bytes per second).

• <HTTPTunnel> contains two tags that affect the latency observed by a client tunneling into the

server (tunneling means to send RTMP packets through HTTP). Low values will reduce the

latency but increase the network bandwidth overhead. The values of the two tags,

<IdlePostInterval> and <IdleAckInterval>, should be considered together: for

applications that need low latency, use a value of 128 for <IdlePostInterval> and 256 for

<IdleAckInterval>; when latency is not an issue, use values of 1024 and 2048, respectively.

The default setting of 512 for both values provides medium latency.

• <IdlePostInterval> specifies the interval, in milliseconds, at which the client should send

idle posts to the server to indicate that the player has no data to send. This interval must be

specified to enable the server to send data to the player. Valid values are between 0 and 4064

milliseconds.

• <IdleAckInterval> specifies the maximum number of millseconds the server waits before

sending an acknowledgement (ack) of a client-idle post. Valid values are between 0 and 4064

milliseconds.

1 2 ... 44 45 46 47 48 49 50 51 52 53 54 ... 59 60

Brak uwag

MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Instrukcja Użytkownika Strona 49