Installation guide

Close idle connections
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
6 or later.
When clients leave an application, their connection is oen le open. Flash Media Server 3.5 can
detect these idle connections and reclaim their resources for new and active clients. When a client
hasbeenidlelongerthanthemaximumspeciedidletime—thedefaultis10minutes—theserver
closes the connection. To enable this feature, you must set AutoCloseIdle-Clients
to true in the Server.xml le. Aer it is enabled in the Server.xml le, you can disable
it for individual virtual hosts or individual applications in the V host.x m l and
Application.xml les.
Limit connection requests
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
6 or later.
Insomecases,ifmanyclientsareattemptingtoconnecttotheserver,thequalityofservicecan
be diminished for those clients who are already connected. By setting the MaxConnection
Rate in the Server.xml le, you can limit the number of connection requests per second that
are accepted.
Send aggregate messages
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
9,0,115,0 or later.
By default, applications break up aggregate messages into individual messages before delivering
them to clients. You can congure applications not to deliver aggregate messages by setting the
AggregateMessages parameter to false in the Application.xml le.
SendingaggregatemessagesreducesCPUusageandincreasesservercapacity.However,itcan
introducesomelatency,soitisnotrecommendedforreal-time,one-to-onecommunication.Itis
recommended for on-demand and live broadcast applications where latency has little eect.
Congure content storage
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
6 or later.
Storagecongurationisimportanttoserverperformance.Ifyourharddiskaccessisnotfast
enough to keep up with the bit rate of your content, your clients receive buer empty messages, and
the overall quality of service suers.
eservercanuselocalornetworkstoragetoservemediales.Inthe Application.xml le,
you can change the default location where streams and shared objects are stored, and map virtual
directories to physical directories on local or network storage to manage your content. is can be
very convenient in team environments, when you may not always want content creators to have
direct access to your Flash Media Server, or if you have a large library of media les that you don’t
want to copy to your Flash Media Server.
Conguring security features
Flash Media Server 3.5 has several security features that you can easily set in the conguration les.
Formoreinformationaboutsecuringyourserverandcontent,seethe“Securityfeatures”section.
Verify SWF les
Enhancement in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash
Player 9,0,115,0 or later.
You can congure the server to verify client SWF les before allowing them to connect to an
application. Verifying SWF les prevents someone from creating their own SWF les that
attempt to stream your content or using your server resources. e server compares the
connecting SWF le with existing SWF les on your Flash Media Server and allows the
connection if there is a match.
41