Adobe 65029121 - Flash Media Streaming Server, Configuration And Administration Manual, Page: 154 / 257

150
FLASH MEDIA SERVER 4.5 CONFIGURATION AND ADMINISTRATION
XML configuration files reference
Last updated 11/28/2012
The following table lists the values available for the
Distribute
element:
Example
<Distribute numproc="1"></Distribute>
See also
Scope
,
LifeTime
,
MaxFailures
,
RecoveryTime
DuplicateDir
Note: This feature has been deprecated.
This is one of two
DuplicateDir
elements in the Application.xml file: one is in the
SharedObjManager
container and
one is in the
StreamManager
container.
Specifies the physical location where duplicate copies of shared objects or recorded streams are stored.
This location serves as a backup for shared object files and recorded stream files. This location must already exist when
a shared object is copied to it.
Example
To include the application name in the paths for the backup files, change the
appName
attribute to
"true".
<DuplicateDir appName="true">c:\backupSharedObjects</DuplicateDir>
<DuplicateDir appName="true">c:\backupStreams</DuplicateDir>
See also
StorageDir
Duration
This element instructs the server how long, in seconds, to wait before it notifies the client when the audio has stopped
in the middle of a live or recorded audio stream.
The default wait time is 3 seconds. The minimum wait time is 1 second. There is effectively no maximum value (the
maximum is the maximum value of a 32-bit integer).
Example
<Duration>3</Duration>
Value Description
vhosts All instances of applications in a virtual host run together in a process.
apps
All instances of an application run together in a process.
insts
Each application instance runs in its own process. This is the default value. If you choose this value, you must also
set the
Distribute numprocs attribute to a value greater than 1.
clients Each client connection runs in its own process.
Use this value for stateless applications—applications that don’t require clients to interact with other clients and
don’t have clients accessing live streams. Most vod (video on demand) applications are stateless because each
client plays content independently of all other clients. Chat and gaming applications are not stateless because all
clients share the application state. For example, if a shared chat application were set to client, the messages
wouldn't reach everyone in the chat because they’d be split into separate processes.