This is a message.


This section describes how to configure streaming in Flowplayer. If you don’t know what streaming is, we recommend you read the installation document’s video server section.

Streaming plugins are also called “providers” and are configured inside the “plugins” node just like all the other plugins discussed in previous sections. They don’t, however, have any display or styling properties because they work in the background and have no visual component. Providers can be thought of as “input plugins”. They are configured in this manner:

plugins: {
// this plugin provides access to servers that support the Real
// Time Messaging Protocol (RTMP)
rtmp: {
// path to provider implementation
url: 'flowplayer.rtmp-3.2.13.swf'
// access to "pseudo-streaming" servers such as lighthttpd
pseudo: {
url: 'flowplayer.pseudostreaming-3.2.13.swf'


Provider Configuration

Having configured a number of different providers, you have to specify which provider to use for each clip. This is done using the provider property in the clip as follows:

clip: {
// by default fetch video data using RTMP
playlist: [
// the first two clips use RTMP
// the third clip comes from a streaming server that supports
// "pseudostreaming"
url: 'movie3.flv',
provider: 'pseudo'
// the fourth clip uses a default HTTP provider that simply
// reads a file from an ordinary web server
provider: 'http'


URL Resolvers and Connection Providers

URL resolvers are used to resolve the final URL that is used when the clip is loaded using a streaming provider. Examples are our bandwidth detection and secure streaming plugins that are both URL resolvers.

Connection providers are used to establish connection to streaming servers. They can also be used to provide a connection to a CDN network. An example is our secure streaming plugin that is configured as a connection provider when it's used to enable secure connections to the Wowza Media Server.

You can also write your own URL Resolvers and Connection Providers if you have a special way to construct the URLs or need special handling when connecting to the server.

Further information