Installation guide

<scope>vhost</scope>

Process scope “vhost.” Useful for applying unique

settings for users in dierent subdomains.

Process scope “app.” Each application running can be run

within its own process. This would be useful if you have

lots of memory, and heavy connection requests from

dierent applications.

Process scope “inst.” Depends on your customer

provision.

ForaCDNcustomer(VODproles),selectionofascopedependsuponhowyouprovisionyour

customeraccounts.ConsiderthateachcustomerisprovisionedasanapplicationwithinFlash

MediaServer.Iftherearealotofcustomers,theappscopemaynotbethebestoption.Each

processscopecanuseamaximumof4GBofRAM,sotoomanyprocessesmaynotbethebest

choice. Alternatively, if you have only a few large customers in your deployment, then the app

scope may be your best choice.

Distributed cores

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

Tofurtherincreasethecapacityandreliabilityofyourserver,youcandistributeconnections

across multiple processes for a specic scope. For example, if your scope was set to adaptor, you

couldhaveconnectionsspreadacrossanynumberofcoreprocessesforeachvirtualhost.Inthe

following gure, there are four core processes for each virtual host. All connections on the single

virtualhostcouldbeevenlydistributedoverthreeprocesses.Ifthereweretwovirtualhosts,

connections could be distributed across six core processes.

Distributed process scopes

There are three processes, each able to accept connec-

tions. Users connected to the same application may not

be able to communicate or share RAM because they

connected to a dierent process. Useful for stateless

deployments.