Installation guide

Built-in bandwidth detection

Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player

6 or later.

Bandwidth detection is built into Flash Media Server and is enabled by default. e updated

approach to bandwidth detection, called native bandwidth detection, provides better performance

and scalability than scripted bandwidth detection. To use native bandwidth detection, simply

make sure bandwidth detection is enabled and write client code that calls functions built into

Flash Media Server. is feature is compatible with ActionScript 2 and 3, and no server-side code

is required.

You can also choose to disable native bandwidth detection and implement detection in a

server-side script, especially if you want to reuse existing code. To use server-side bandwidth

detection, use the specialized main.asc le Adobe provides for bandwidth detection and

disable native bandwidth detection in the Application.xml le. For more information,

refer to the Adobe Flash Media Interactive Server 3.5 Developer Guide.

Process scopes

Feature in Flash Media Interactive Server; requires Flash Player 6 or later.

FlashMediaInteractiveServer3.5givesyoucontroloverhowserverprocessesareallocated.

When you start the server, you are starting a process called F M S M a st e r.e x e (Windows)or

fmsmaster (Linux).ApplicationinstancesruninprocessescalledFMSCore.exe(Windows)

or fmscore(Linux).

Flash Media Server operates with multiple processes. With the default installation, four processes

are running: master,Edge,core, and admin.

emasterprocessisamonitorthatstartscoreprocesseswhennecessary.Onlyonemaster

process can be running at a time, but many core processes can be running. You can congure

how applications are assigned to server processes in the Application.xml le. You can

specify the number of processes, the process scope, how long a process runs, and the number of

process failures allowed before a core process is disabled.

ClientsalwaysconnectthroughtheEdgeprocess(whetherornotanEdgeorOriginconguration

exists).emasterprocessisresponsibleforspawningandrollingovereachcoreprocess.Clients

never connect to the master process, and the master process cannot be congured. e following

gureillustratesthemaster,core,andEdgeprocesses.

Illustration of process scopes