Streams

You can specify multiple virtual directory mappings for streams by adding additional Streams tags--one for each virtual directory mapping.

Example

<Streams>foo;c:\data</Streams>

This example maps all streams whose names begin with foo/ to the physical directory c:\data. The stream named foo/bar would map to the physical file c:\data\bar.flv.

If there is a stream named foo/bar/x then Flash Media Server first tries to find a virtual directory mapping for foo/bar. If there is no virtual directory for foo/bar, Flash Media Server then checks for a virtual directory mapping for foo. Since a virtual directory mapping does exist for foo, the stream foo.bar maps to the file c:\data\bar\x.flv.

Syntax

virtualDirectory;actualDirectory

The Streams tag allows you to specify a virtual directory for stored stream resources used by more than one application. By using a virtual directory, you specify a relative path that points to a shared directory that multiple applications can access.

Example

<Streams>common;C:\FlashMediaServer\myApplications\shared/resources\
</Streams>

If the virtual directory you specify does not end with a backward slash, one is added by the server.

Any application that refers to a stream whose path begins with common/ will access the item in C:\FlashMediaServer\myApplications\shared\resources regardless of the application's own directory structure. If the application VideoConference refers to an item common/video/recorded/June5 and the application Collaboration refers to common/videorecorded/June5, they both point to the same item
C:\FlashMediaServer\myApplications\shared\resources\video\recorded\June5\.

Additional information

This release includes a feature called custom stream delivery, which allows Flash Media Server to match the decoding of a recorded stream to the version of Flash Player on the client. Custom stream delivery allows an application running on Flash Media Server to switch between the Sorenson and On2 CODECs (data COmpressor/DECompressor) without changes to the code.

Custom stream delivery is enabled using a combination of the VirtualDirectory and VirtualKey tags, and the Client.virtualKey and Stream.setVirtualPath() APIs.

For instance, the application developer might locate a stream encoded with the On2 codec in one folder and create a different folder for the same stream encoded with the Sorenson codec. Both streams have the same content, but each is tailored to replay on specific versions of Flash Player.

You specify more than one virtual directory mapping by adding multiple Streams tags.

Example

<VirtualDirectory>
    <Streams key="A">foo;c:\streams\on2</Streams>
    <Streams key="B">foo;c:\streams\sorenson</Streams>
    <Streams key="">foo;c:\streams</Streams>
</VirtualDirectory>

The Key attribute matches the key found in the Flash Player string FlashVer on the client, which is automatically sent to Flash Media Server with the login.

The administrator sets the key. The client object in the server-side script has the writable client.virtualKey property. Flash Player 8 and Flash Player 9 are assigned Key A; earlier versions of the player get Key B. When the client plays a stream, it will use the appropriate key. The replay of a recorded stream fails if the player does not find a key.

Streams

Description

Example

Syntax

Example

Additional information

Example

See also