
Chapter 212
An optional Application.xml file in the application’s directory in the flashcom application directory.
If present, this file provides specific settings for the application that may be different from the
settings in the server’s primary Application.xml file. For more information about the server’s
configuration files, see About the configuration files.
Optional server-side scripts. Some applications may make use of Server-Side Communication
ActionScript. If server-side scripts are used, they are located in the application’s directory in the
flashcom application directory or in the directory specified in the
<ScriptLibPath> tag in the
application’s optional Application.xml file. These scripts may have file extensions of .js or .asc.
Optional audio and/or video stream files. Some applications may make use of preexisting audio/
video streams or may record them to disk. Stream files have the extension .flv. These files are
located in a directory named Streams inside the application’s directory in the flashcom application
directory or in the directory specified in the
<StreamManager>:<StorageDir> tag in the
application’s optional Application.xml file.
Optional shared object files. Some applications may make use of preexisting shared objects or may
write them to disk. Shared objects contain nonstreaming data that is used by more than one client
of a communication application. Shared object files have the extension .fso. These files are located
in a directory named Sharedobjects inside the application’s directory in the flashcom application
directory or in the directory specified in the
<SharedObjManager>:<StorageDir> tag in the
application’s optional Application.xml file. Shared objects can also exist on the client side. For
more information about using shared objects, see Developing Communication Applications.
Understanding basic server settings
When Flash Communication Server is first installed, it’s configured in a generic way so that you
can begin using it with the sample client applications. You should become familiar with this
configuration so that you can make decisions about how to change it to suit your needs.
The server is installed with a set of configuration files in XML format. These files define a default
server adaptor, a default flashcom application directory, default server administrators, and default
settings for application behavior.
The default server adaptor uses port 1935, the number assigned to Flash Communication Server
by the Internet Assigned Numbers Authority (www.iana.org). Although you can use any port
number, this increases the risk of conflicting with another application that may be assigned to the
same port. Applications must be authored to use the same port the server is using. Be sure the
port is set to the open state.
The server is preconfigured with one adaptor containing one virtual host. The virtual host is
equivalent to a domain name. The default application directory for the default virtual host is the
the flashcom applications directory. If you chose Developer Install during installation, this
directory is under \flashcom\applications. You can view this location by looking at the value for
the AppsDir tag in the vhost.xml file. This directory is where the server will look for application
subdirectories at startup; you must place an application subdirectory here for each client
application that you plan to connect to the server, and the client subdirectory must have the same
name as the client application. The presence of the application subdirectory registers the
application with the server.
Commentaires sur ces manuels