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

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 369
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 61
Configuring Flash Communication Server 41
<AppsDir> specifies the path to the flashcom application directory for this virtual host. The
application directory must contain a subdirectory for each application that will run on the
server. This tag allows you to locate your application directories outside the virtual host
directory if you wish. If no application directory is specified, it defaults to C:\Program
Files\Macromedia\Flash Communication Server MX\conf\_defaultRoot_\_defaultVHost_\.
To run on the server, each application must have a directory named with the name of the
application inside the flashcom application directory. For example, if you have an application
named VideoConference and another named Collaboration and you specify the path
C:\MyApps in the
<AppsDir> tag, then the directories C:\MyApps\VideoConference\ and
C:\MyApps\Collaboration\ must exist.
Be sure to include a directory named admin in each virtual host’s flashcom application
directory. This ensures that the Administration Console (admin.swf) will be able to connect to
the virtual host. For more information, see Using the Administration Console.
The default Vhost.xml file installed with Flash Communication Server contains your
application directory name. If you chose Developer Install during installation, the application
path is \flashcom\applications\ under the publishing directory of your web server if you have
one installed. If you do not have a web server installed, or if you chose Production Install
during installation, the default directory is under C:\Program files\Macromedia\Flash
Communication Server MX\flashcom\applications\. The server-side flashcom application
directory (containing your ASC, FLV, and FLA files) should be separated from your web root
directory when you deploy the server and applications. Only your SWF and HTML files
should be inside the web publishing directory.
<RecordAccessLog> indicates whether the server should (true) or should not (false) record
connections to the server. This information is written to an access.flv file in the virtual host’s
admin\Streams\Logs\ directory inside its application directory.
<ResourceLimits> is a container tag for the next five tags. By specifying values for these five
tags, you can ensure that the server does not consume excessive resources for the virtual host,
and you can prevent denial of service attacks to the server.
<MaxConnections> specifies the maximum number of simultaneous connections allowed on
this virtual host. Connections are denied if the specified limit is exceeded. The default of -1
allows an infinite number of connections. If you supply a different value, it must be a positive
integer. If you specify a negative or non-numeric value, the default is used. This value can be
changed at runtime.
<MaxAppInstances> specifies the maximum number of application instances that can be
loaded by this virtual host. (A chat application, for example, might require more than one
instance, because each chat room would be represented by a separate instance of the
application on the server.) A Flash movie defines which application instance it is connecting to
by the parameters it includes with its ActionScript
connect call.
The default value of -1 allows an infinite number of application instances. If you specify a
different value, it must be a positive integer. This value can be changed at runtime.
<MaxStreams> specifies the maximum number of streams that the virtual host can create. The
default value of -1 allows an infinite number of streams. If you supply a different value, it must
be a positive integer. This value can be changed at runtime.
Vue de la page 61
1 2 ... 57 58 59 60 61 62 63 64 65 66 67 ... 368 369

Commentaires sur ces manuels

Pas de commentaire