Contents Of The Dictionary - MACROMEDIA FLASH COMMUNICATION SERVER MX-SERVER-SIDE COMMUNICATION ACTIONSCRIPT DICTIONARY Manual

Naming applications
Flash Communication Server application names must follow the Uniform Resource Identifier
(URI) RFC 2396 convention (see http://www.w3.org/Addressing/). This convention supports a
hierarchical naming system where a forward slash (/) separates the elements in the hierarchy. The
first element specifies the application name. The element following the application name specifies
the application instance name. Each instance of the application has its own script environment.
Specifying instances
By specifying a unique application instance name after an application name, you can run multiple
instances of a single application. For example, rtmp:/support/session215 specifies a customer
support application named "support" and refers to a specific session of that application named
"session215". All users who connect to the same instance name can communicate with each other
by referencing the same streams or shared objects.
Using JavaScript syntax
You must follow all syntax rules of JavaScript. For example, JavaScript is case-sensitive and does
not allow punctuation other than underscores (_) and dollar signs ($) in names. You can use
numbers in names, but names cannot begin with a number.
Avoiding reserved commands
Flash Communication Server has reserved commands that you cannot use in a script. These
commands are either that methods belong to the client-side NetConnection object or methods
that belong to the server-side Client object. This means that if you have a NetConnection object
on the client (player), you cannot make the following call:
nc.call( "reservedCmd", ... );
In this call,
"reservedCmd"
,
createStream deleteStream
, or
receiveVideo
getBandwidthLimit

Contents of the dictionary

All dictionary entries are listed alphabetically. However, methods, properties, and event handlers
that are associated with an object are listed along with the object's name—for example, the
property of the Application object is listed as
locate these elements.
ActionScript element
acceptConnection
addHeader
agent
application
bufferTime
call
clear
is any of the following commands:
,
onStatus
. It also cannot be any of the server-side Client object methods:
seek
,
setBandwidthLimit
See entry
Application.acceptConnection
NetConnection.addHeader
Client.agent
Application (object)
Stream.bufferTime
Client.call, NetConnection.call
SharedObject.clear, Stream.clear
closeStream
, , ,
pause play publish
, , and
getStats ping
Application.name
Server-Side Communication ActionScript
, ,
connect
, ,
receiveAudio
.
. The following table helps you
name
7