MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Spécifications télécharger pdf (Page 93)

About Flash Communication Server 15

The flashcom application directory

When your Flash application requires the Flash Communication Server, you must place your

application data where the server can locate it.

During installation, you choose either a Developer Install or a Production Install of the Flash

Communication Server. In both cases, if you don’t have a Web server installed, the default

directory is C:\Program files\Macromedia\Flash Communication Server

MX\flashcom\applications for both client-side application files—SWFs and HTMLs—and

server-side application files—ASC files, recorded stream (FLV) and remote shared object (FSO)

files, and your FLA source files.

• If you choose Developer Install, you can specify a different default directory during

installation, but Flash Communication Server will expect to find both client-side and server-

side files in subdirectories this directory. The advantage of choosing Developer Install is that

you can run the samples and test your applications from a single directory in the

\flashcom\applications directory that has the same name as your application. That is, for

convenience during development, client-side application files are stored in the same directory

with your server-side application files.

• If you choose Production Install, you can specify a different default directory for client-side

files and a different default directory for server-side files. Flash Communication Server will

know where to look for the files it needs. The advantage of choosing Production Install is that

your client-side application files can be accessible through a web server, while your server-side

application files will not be accessible to a user browsing your Web site.

For organizational purposes during your development work, it’s convenient to store all your client

and server application files (FLA, SWF, HTML, and ASC) in this subdirectory. When you deploy

your application, you can place your SWF and HTML files in any location. However, the

chat_App subdirectory must remain on the server, along with any ASC files used by the

application. The server-side files (your ASC, FLV, FSO, and FLA files) should not be in your web

root directory when you deploy the server and applications. Only your SWF and HTML files

should remain inside the web publishing directory.

If you chose Developer Install and then want to deploy your applications on the same machine,

you’ll want to separate client files from your server-side files. To do so, you can either reinstall the

server (choosing Production Install) and then relocate your files to the appropriate locations, or

you can change the configuration settings in the administration XML files as described in

Managing Flash Communication Server and then relocate your files to the appropriate locations.

In all cases, you must create a directory in the server-side directory that has the same name as the

application you connect to when issuing the

NetConnection.connect command.

For example, suppose you have an application called chat_App:

NetConnection.connect("rtmp://myServer.myDomain.com/chat_app")

You must create a subdirectory named chat_App in your server-side flashcom application

directory. Suppose also that this application uses some server-side scripting stored in a file called

main.asc. You must place main.asc in this same directory.

Note: You must create a subdirectory that matches your application name even if you have no server-side script files

to place there. This is because Flash Communication Server stores any stream or shared object files created by your

application in subdirectories of this directory (see “File types and paths” on page 67). Also, the existence of this

directory tells the Flash Communication Server that the application is authorized and that users can connect to

instances of this application.

1 2 ... 88 89 90 91 92 93 94 95 96 97 98 ... 368 369

MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Spécifications Page 93

Commentaires sur ces manuels

MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Spécifications Page 93

Commentaires sur ces manuels

Produits connexes et manuels pour Serveurs MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY