Managing the Server > Performing administration tasks > Understanding application elements

Understanding application elements

It is important to understand the files, scripts, and other parts of a communication application that runs on the server. These elements include the following:

A Macromedia Flash MX SWF file. This is the user interface to the application. The SWF file can be served from a web server or even distributed to users in other ways, such as e-mail.

A directory inside the applications directory, named to match the application name. This is the registered application directory and is what the SWF file uses when connecting to Flash Communication Server. For more information about the applications directory, see Registering client applications.

An optional Application.xml file in your application directory in the applications directory in the Flash Communication Server 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. Most communication applications will need Server-Side Communication ActionScript. If you use server-side scripts, put them in the registered application directory in the applications 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 or .mp3 and are located in the /streams/instance_name directory within the registered application directory in the /applications 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 and are located in the /sharedObjects/instance_name directory within the registered application directory in the applications 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 Help.

Tip: Macromedia recommends you use all lowercase letters and no spaces when naming directories and files used with Flash Communication Server and its applications. This practice helps to ensure that, during development, your applications will work if you move files to different computers on different platforms.