![]() |
You can deliver content from a server running Windows Media Services or from a Web server to a player. The server and player can be either on the Internet or an intranet, and they can be separated by a firewall. Although a Windows Media server is designed specifically for streaming Windows Media-based content, a standard Web server is not. If you decide to use a Web server, you should be aware of the differences in the way the content is delivered, which can affect the quality of the playback.
A Windows Media server meters the delivery of packets according to feedback information it receives while sending a stream to a player. When a player receives packets in this way, the presentation is much more likely to be smooth. Because bandwidth use is controlled, more users can connect concurrently to your site and receive streams that are free of interruptions.
If you plan to deliver your content as a
When streaming single-bit-rate streams or files, a Windows Media server is designed to handle network congestion smoothly. If congestion occurs during the broadcast, the stream is "thinned", which means that the frame rate is reduced. If this is insufficient, the video portion of the stream is frozen and only the audio portion is streamed.
A Web server is designed to download as much data as it can, as quickly as possible. This is the preferred method for sending packets containing static images, text, and Web page script, but it is not the best method for sending packets containing streaming media. Streaming media should be delivered in real time, not in large bursts, and the player should receive packets just ahead of rendering them.
Web servers do not support MBR streams. When a file streams from a Web server, the quality of the delivery is not monitored and no adjustment to the bit rate can be made. Web servers cannot use the preferred delivery protocol,
Note