Protocols: HTTP vs. RTMP
When you use the FLV file format as your distribution method for Flash Video content, you have two options for serving the Flash Video over the Internet: HyperText Transfer Protocol (HTTP) and Real Time Messaging Protocol (RTMP). You can use one or both protocols to serve Flash Video to your Internet audience.
Most content viewed on a Web site is served over HTTP. Any Web server, such as Apache or Microsoft Internet Information Services (IIS), can deliver Flash Video (FLV or SWF) files. The best reasons to use a Web server with HTTP protocol for hosting Flash Video content are simplicity and cost. If you know how to transfer files to a Web server using a File Transfer Protocol (FTP) client, for example, you can put Flash Video files on a Web site and make the content accessible to visitors. Another advantage of HTTP is cost: Most Web hosting providers offer cheap storage and large transfer quotas that allow you to host numerous media files and serve them to your visitors.
From a site visitor's point of view, one advantage of using HTTP is access. Many corporate networks use firewalls to block specific content from entering. Popular methods of blocking are protocol and port restrictions. Some firewall rules allow only HTTP content served over port 80. Almost all Web servers use port 80 to serve content, but a Web server can be set up to serve HTTP content over custom ports such as 8080, 8081, or 8500. These ports are usually used by test or development servers. Some firewall rules allow only specific MIME types, such as text/html (HTML documents), and common image formats (image/gif, image/jpeg, and image/png). By far, Flash Video served over HTTP on port 80 has the best chance of being viewed by a visitor.
However, Flash Video content delivered using HTTP lacks intellectual property (IP) protection. There is no way to limit offline access to Flash Video content served over HTTP: The Web browser caches Flash Video files in its temporary storage, which can be accessed by the user after browsing the site. As such, content producers and licensees don't distribute Flash Video content over HTTP; RTMP is the preferred protocol.
Another drawback to HTTP-delivered Flash Video is access to all parts of the video file. With Flash Video served over HTTP, the video file (FLV or SWF) progressively downloads to the Web browser's cache. The viewer can access only the portion of the video that has already downloaded. For example, if you have a 30-minute training video, and the viewer wants to view only the last five minutes of the video, they have to wait until the first 25 minutes have downloaded to the browser cache. For longer videos, you should consider using RTMP instead of HTTP.
You can serve Flash Video over the Internet using RTMP, a special protocol for real-time server applications ranging from instant messaging to collaborative data sharing to video streaming. Whereas HTTP-delivered Flash Video is referred to as progressive download video, RTMP-delivered Flash Video is called streaming video. However, because the term streaming is so often misused, I prefer the term real-time streaming video.
RTMP delivery of Flash Video is provided by licensed server software from Adobe, notably Flash Media Server (FMS). FMS is installed on a networked server and manages streaming Flash Video separately from the Web server hosting the Flash movie (SWF) and other HTML content (see Figure 4.1). Licensing FMS for high volume Web sites, though, can be prohibitively expensive, but you can find affordable shared hosting FMS services for less demanding sites from providers such as Influxis.com. Using a Flash Video Streaming Service (FVSS) provider is a better option for high volume Flash Video deployment, and I discuss this option later in the chapter.
Figure 4.1 When a user views real-time streaming Flash Video content, a Flash movie (SWF) is downloaded from a Web server (step 1), and a NetConnection instance created in the movie's ActionScript code makes a connection to the FMS application or FVSS provider (step 2). The Flash Video content (FLV) is then streamed packet by packet to the Flash Player (step 3).
One of the benefits of RTMP delivery for the viewer is near-instantaneous playback of video, provided the Flash Video file is encoded with a bitrate appropriate to the viewer's connection speed. Real-time streaming video can also be seeked to any point in the content. This feature is particularly advantageous for long-duration content because the viewer doesn't have to wait for the video file to load before jumping ahead, as is the case for HTTP-delivered video.
Content producers who want to protect video from local playback can opt to use real-time streaming video—in any video format, not just Flash Video. When RTMP-based video streams into the Flash Player, the audio and video data is only stored in the Flash Player's memory buffer. The entire Flash Video file is never copied or stored to the Web browser cache.
The protocol you use can affect your Flash Video deployment strategy. Be sure to carefully analyze your objectives before picking a protocol.
If you encode your Flash Video files with a compression tool, you should determine which protocol(s) to use before you create the FLV files. Because RTMP connections send video data from a remote server to a temporary player buffer, the Flash Video's data rate should be predictable throughout the entire duration of playback. This data rate consistency can only be accomplished with constant bitrate (CBR) encoding. Nearly all Flash Video encoders offer the option of selecting constant bitrate or variable bitrate (VBR) encoding. If your Flash Video encoding tool doesn't offer a choice, it's probably using CBR encoding.
If your Flash Video content is encoded with a VBR setting, your file may have extreme data spikes that exceed the average bitrate of the video. These spikes can abruptly empty the Flash Player's buffer and result in temporarily stalled playback and an annoying pause-play-pause experience.
However, if your Flash Video content won't be delivered over RTMP, you can safely use VBR encoding for standard HTTP delivery on a Web server. Because the Flash Video progressively downloads and is stored in the Web browser cache, data spikes probably won't occur during playback—provided the bitrate you're using is suitable to the viewer's connection speed.
For security reasons, some internal networks, or intranets, control the type of content that can enter the network from remote locations. In large corporations, these intranets can block much of the content available on the Web. Firewalls and proxies that allow Internet traffic accept HTTP connections over port 80 from remote servers, so you're nearly guaranteed that viewers behind these firewalls can access Flash Video delivered over HTTP.
However, this luxury isn't always shared with RTMP-delivered Flash Video. The default port for RTMP connections is 1935, which may not be allowed on tight firewalls. If the Flash Player's first attempt to play video over port 1935 fails, the Flash Player automatically tries to connect to the video stream with RTMP over port 80. If this second try fails, the last resort available for the Flash Player is to try an HTTP-tunneled connection over port 80. A tunneled connection means the RTMP data packet is wrapped (or masked) in an HTTP data packet. Some firewalls allow this traffic, because the data packet appears to be normal HTTP Web traffic. If the firewall inspects the HTTP data, though, it still may reject the connection, and the Flash Video won't play.
The bottom line: If you don't want to deal with firewalls and proxies, you should serve your Flash Video from a Web server over HTTP.
Some video formats available over the Internet use digital rights management (DRM) to control access. Microsoft Windows Media and Apple QuickTime use encrypted keys to limit many factors of media usage, including the number of computers that can view the content and how long the content can be viewed. Flash Video hasn't included such ironclad content protection measures in any past releases of the Flash Player, including Flash Player 9.
If you must control access to Flash Video content, and you don't want users to fish FLV files out of their Web browser cache, you must use real-time streaming Flash Video. As soon as you put your FLV files in a publicly accessible location on a Web server, you're allowing users to copy the FLV files and do whatever they want with them. Mind you, lots of Flash Video files on the Web—even from high-volume sites—aren't real-time streaming Flash Video. Google's Video search and YouTube.com are prime examples of sites offering browser-cacheable, do-as-you-please FLV files. However, real-time streaming Flash Video is usually the only viable option for companies and organizations (such as movie studios and broadcast networks) that need to control the way their content is viewed and accessed by the public.
Online or offline playback
If your Flash application is designed to run from a local source such as a user's hard drive or fixed media (CD/DVD-ROM), you may want the Flash Video content to coexist with other local files used for the application. Unless you want to require an Internet connection for the Flash application to run, you don't need to store Flash Video files on remote Web servers (HTTP) or real-time streaming servers (RTMP).
Duration of content
As the length of a video file increases, so should the likelihood of using real-time streaming Flash Video (RTMP) over a progressively downloaded Flash Video (HTTP). Regardless of the data rate used by the video file, longer files have larger file sizes. When an HTTP-delivered Flash Video starts to download into the Flash Player, by default the file continues to download to the browser cache regardless of whether the user watches the content. If you host large FLV files on your Web server, the Web server's data-transfer bytes will increase quickly, potentially raising the financial cost of hosting the files. If you host large FLV files on an FMS (or Flash Video Streaming Service), your data-transfer cost includes only the portions of the Flash Video watched by each user.