The tables in this appendix summarize link formats for each type of delivery method and content type.
For more information on creating links in general, consult Chapter 5, "Understanding Link Formats".
Link formats shown are based on default values included with RealServer.
 |
Note |
|
If you change or add a mount point, or change the port
numbers, remember to use the new values in your links.
And be sure to tell anyone else who creates links, too.
|
The Subject of a Link
When creating a link in a Web page, remember that you do not actually link to the clip itself; you link to a metafile that references it-either a Ram file, a SMIL file, or the automatically generated Ram file. For each type of content, two types of links are shown:
- a link in a Web page, which starts with
http://
- a link that can be typed directly in RealPlayer, or used in a Ram or SMIL file, or created by Ramgen. This type starts with
rtsp://
For this second type of link, the format is nearly the same as the link used in the Web page, with three exceptions: the protocol is different, the port number (if any) matches the protocol, and Ramgen is omitted.
The format you use for the link depends on two factors:
- where you will put the link (in a Web page, a Ram or SMIL file, or by typing it into RealPlayer)
- whether you are linking to clips or to metafiles
The table below summarizes the differences:
Location of and Type of Link
| Location of Link |
File Type |
Formats |
Protocol |
| Web page |
media clip |
Ramgen mount point |
http |
| metafile |
no special format |
http |
| Ram or SMIL file, RealPlayer |
media clip |
no special format |
rtsp or pna |
Links to scalable multicasts are different in two ways:
- Ramgen mount point is not used
- http protocol is always used, regardless of whether the link appears in a Web page or in RealPlayer
How Authenticated Content Is Different
The tables in this appendix show how to construct a link to that type of authenticated content.
Two factors distinguish authenticated content from regular content:
- On-demand content must be stored in a different location than regular content, and it must not be a subdirectory of the main base path.
- The content creator must include
/secure/ as part of its path in the encoding software.
- The link must include the mount point
/secure/.
|
|
Note |
|
Merely adding the secure mount point to a link does not
mean the material will be authenticated. You must set
up the authentication feature, and create the correct
links, for authentication to work.
|
Multiple Mount Points in Links
When you are combining several features at once, the following guidelines will help you to decide the order in which the relevant mount points should appear in your link:
- When
ramgen is used in a link, it is the first mount point.
- When
encoder is used in a link, it is always the last mount point. Everything to the right of the encoder mount point is considered path information.
- The mount point
secure should appear just before the file name (for on-demand clips) or just before the encoder mount point (for live clips). If you place it ahead of the ramgen mount point, the Web browser will perform the authentication, rather than RealServer.
Port Numbers in Links
If you change the port numbers for RTSP Port, PNA Port and HTTP Port from their default values, you will need to tell your users so that they can include the new ports in their links. (If a link does not include a port number, RealPlayer uses default values for contacting the RealServer. But if RealServer is no longer listening on those ports, it will not receive the request.) See "Port Numbers" for more information.
On-Demand Content
|
|
| Mount points |
ramgen
|
| Link in Web page |
http://address:HTTPPort/ramgen/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/presentation/presentation.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/path/file
|
| Example |
rtsp://realserver.example.com:554/presentation/presentation.rm
|
| Reference |
"Linking to On-Demand Clips" |
| Authenticated Content |
| Mount points |
ramgen, secure |
| Link in Web page |
http://address:HTTPPort/ramgen/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/secure/concerts/summer/mozart.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/secure/path/file |
| Example |
http://realserver.example.com:8080/ramgen/secure/concerts/summer/mozart.rm |
| Reference |
"Step 4: Linking to Authenticated Content". |
Account-Based ISP Hosted Content
|
|
| Mount points |
ramgen |
| Link in Web page |
http://address:HTTPPort/ramgen/~account/path/file |
| Example |
http://realserver.example.com:8080/ramgen/~schu/music.rm |
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/~account/path/file |
| Example |
rtsp://realserver.example.com:554/ramgen/~schu/music.rm |
| Reference |
"Step 3: Linking to ISP Content". |
| Authenticated Content |
| Mount points |
Authentication is not available for users' content. See "ISP Hosting Used with Other Features". |
| Link in Web page |
| Link within Player, Ram files, SMIL files |
| Reference |
Dedicated ISP-Hosted Content
|
|
| Mount points |
ramgen
|
| Link in Web page |
http://address:HTTPPort/ramgen/directory1/directory2/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/s/sc/schu/music.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/directory1/directory2/path/file |
| Example |
rtsp://realserver.example.com:554/s/sc/schu/music.rm
|
| Reference |
"Dedicated Hosting Server" |
| Authenticated Content |
| Mount points |
Authentication is not available for users' content. See "ISP Hosting Used with Other Features". |
| Link in Web page |
| Link within Player, Ram files, SMIL files |
Ad Streaming with Automatic SMIL Generation
|
|
| Mount points |
adtag/general, smilgen/banner, smilgen/leadin, smilgen/rbanner |
| Link in Web page |
http://address:HTTPPort:8080/ramgen/adtag/general/smilgen/banner
/path/file |
| Example |
http://realserver.example.com:8080/ramgen/adtag/general/smilgen/banner
/g2video.rm
|
| Link within Player, Ram files |
rtsp://address:RTSPPort/adtag/general/smilgen/banner/path/file |
| Example |
rtsp://realserver.example.com:554/adtag/general/smilgen/banner/g2video.rm
|
| Reference |
"Understanding SMIL Generation Mount Points" |
| Authenticated Content |
| Mount points |
ramgen, adtag/general, smilgen/banner, smilgen/leadin, smilgen/rbanner |
| Link in Web page |
http://address:HTTPPort/ramgen/adtag/general/smilgen/secure/path/file |
| Example |
http://realserver.example.com:8080/ramgen/adtag/general/smilgen/secure
/g2video.rm |
| Link within Player, Ram files |
rtsp://address:RTSPPort/adtag/general/smilgen/secure/path/file |
| Example |
rtsp://realserver.example.com:554/adtag/general/smilgen/secure/path/file |
| Reference |
"Using Authentication with Ad Streaming" |
Ad Streaming with SMIL Files
|
|
| Mount points |
adtag/general |
| Link in Web page |
http://address:HTTPPort:ramgen/ramgen/adtag/general/path/file |
| Example |
http://address:HTTPPort:ramgen/ramgen/adtag/general/g2video.smi
|
| Link within Player, Ram files |
rtsp://address:RTSPPort/adtag/general/path/file |
| Example |
rtsp://realserver.example.com:554/adtag/general/g2video.smi
|
| Reference |
"Requesting SMIL Files from an Ad Server" |
Unicasted Live Content (from Encoders)
|
|
| Mount points |
ramgen, encoder |
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/live.rm
|
|
Reference |
"Creating the Link to the Live Unicast" |
| Authenticated Content |
| Mount points |
ramgen, secure, encoder |
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content" |
Unicasted Live Content (from pre-G2 Encoders)
|
|
| Mount points |
ramgen, live |
| Link in Web page |
http://address:HTTPPort/ramgen/live/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/live/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/live/path/file
|
| Example |
rtsp://realserver.example.com:554/live/live.rm
|
|
Reference |
"Creating the Link to the Live Unicast" |
| Authenticated Content |
| Mount points |
ramgen, secure, live |
| Link in Web page |
http://address:HTTPPort/ramgen/live/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/live/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/live/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/live/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content" |
Live content from encoders designed before RealSystem 6 (such as RealEncoder and RealProducer 5) uses the /live/ mount point.
Archived Live Content
|
|
| Mount points |
ramgen
|
| Link in Web page |
http://address:HTTPPort/ramgen/Archive/file
|
| Example |
http://realserver.example.com:8080/ramgen/Archive/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/Archive/file
|
| Example |
rtsp://realserver.example.com:554/Archive/live.rm
|
| Reference |
"Linking to Archived Files"
|
| Authenticated Content |
| Mount points |
ramgen, secure |
| Link in Web page |
http://address:HTTPPort/ramgen/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content". |
If the live content is being created by a pre-G2 encoder, substitute /live/ for /encoder/.
|
|
Note |
|
Secure archived content must be stored in a different
location than archived material available to everyone.
|
Broadcasts that Use G2SLTA as the Source
|
|
| Mount points |
ramgen, encoder
|
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/live.rm
|
| Reference |
"Step 4: Linking to the Simulated Live Broadcast"
|
| Authenticated Content |
| Mount points |
ramgen, encoder, secure |
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content" |
If the live content is being created by a pre-G2 encoder, substitute /live/ for /encoder/.
Redundant Live Content
|
|
| Mount points |
ramgen, redundant |
| Link in Web page |
http://address:HTTPPort/ramgen/redundant/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/redundant/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/redundant/path/file
|
| Example |
rtsp://realserver.example.com:554/redundant/live.rm
|
|
Reference |
"Linking to Redundant Content" |
| Authenticated Content |
| Mount points |
ramgen, secure, redundant |
| Link in Web page |
http://address:HTTPPort/ramgen/redundant/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/redundant/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/redundant/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/redundant/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content" |
Split Content (Push Split)
|
|
| Mount points |
ramgen, broadcast, encoder
|
| Link in Web page |
http://Receiver:HTTPPort/ramgen/broadcast/TransmitterSourceName/path/file
|
| Example |
http://realserver.example.com.au:8080/ramgen/broadcast/Japan/encoder/concert.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://Receiver:RTSPPort/broadcast/TransmitterHostName/path/file
|
| Example |
rtsp://realserver.example.com.au:554/broadcast/Japan/encoder/concert.rm
|
| Reference |
"Step 3: Linking to Split Content". |
| Authenticated Content |
| Mount points |
Split material can be authenticated, but it requires elaborate measures. See "Authentication and Splitting". |
| Link in Web page |
| Link within Player, Ram files, SMIL files |
Split Backup Transmitter Content (Push Split)
|
|
| Mount points |
ramgen, broadcast
|
| Link in Web page |
http://Receiver:HTTPPort/ramgen/broadcast/*/path/file
|
| Example |
http://realserver.example.com.au:8080/ramgen/broadcast/*/concert.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://Receiver:RTSPPort/broadcast/*/path/file
|
| Example |
rtsp://realserver.example.com.au:554/broadcast/*/concert.rm
|
| Reference |
"Linking to Backup Transmitters". |
Pull Split Content
|
|
| Mount points |
ramgen, split, encoder
|
| Link in Web page |
http://Receiver:HTTPPort/ramgen/broadcast/SourcePath/Transmitter:PullListenPort/encoder/path/file
|
| Example |
http://realserver.example.com.au:8080/ramgen/broadcast/
realserver.example.com.jp:2030/encoder/concert.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://Receiver:RTSPPort/broadcast/SourcePath/Transmitter:PullListenPort/encoder/path/file
|
| Example |
rtsp://realserver.example.com.au:554/ramgen/broadcast/pull
/realserver.example.com.jp:2030/encoder/concert.rm
|
| Reference |
"Linking to Pull Split Content" |
| Authenticated Content |
| Mount points |
Split material can be authenticated, but it requires elaborate measures. See "Authentication and Splitting". |
| Link in Web page |
| Link within Player, Ram files, SMIL files |
Back-Channel Multicast Content
|
|
| Mount points |
ramgen, encoder
|
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/live.rm
|
| Reference |
"Linking to Back-Channel Multicasts" |
| Authenticated Content |
| Mount points |
ramgen, encoder, secure |
| Link in Web page |
http://address:HTTPPort/ramgen/encoder/secure/path/file
|
| Example |
http://realserver.example.com:8080/ramgen/encoder/secure/live.rm
|
| Link within Player, Ram files, SMIL files |
rtsp://address:RTSPPort/encoder/secure/path/file
|
| Example |
rtsp://realserver.example.com:554/encoder/secure/live.rm
|
| Reference |
"Step 4: Linking to Authenticated Content" |
If the live content is being created by a pre-G2 encoder, substitute /live/ for /encoder/.
Scalable Multicast Content
|
|
| Mount point |
scalable |
| Link in Web page |
http://address:HTTPPort/scalable/path/file.rm.sdp
|
| Example |
http://realserver.example.com:8080/scalable/concert.rm.sdp
|
| Link within Player, Ram files, SMIL files |
http://address:HTTPPort/scalable/path/file.rm.sdp
(same as link in Web page) |
| Example |
http://realserver.example.com:8080/scalable/concert.rm.sdp
(same as link in Web page)
|
| Reference |
"Linking to Scalable Multicasts" |
| Authenticated Content |
| Mount points |
scalable, secure |
| Link in Web page |
http://address:HTTPPort/scalable/secure/path/file.rm.sdp
|
| Example |
http://realserver.example.com:8080/scalable/secure/concert.rm.sdp
|
| Link within Player, Ram files, SMIL files |
http://address:HTTPPort/scalable/secure/path/file.rm.sdp
(same as link in Web page) |
| Example |
http://realserver.example.com:8080/scalable/secure/concert.rm.sdp
(same as link in Web page)
|
| Reference |
"Step 4: Linking to Authenticated Content" |
Scalable multicast links use a slightly different format than other links:
- Links point to a .sdp file, rather than to the actual live file. The Server automatically generates the .sdp file when a user clicks the link.
- Links do not include the
encoder mount point because information about the nature of the broadcast is included in the .sdp file.
- Ramgen is not used in these links.
If the live content is being created by a pre-G2 encoder, substitute /live/ for /encoder/.
Ram Files
|
|
| Mount points |
none, for most links |
| Link in Web page |
http://address:port/path/file.ram
|
| Example |
http://webserver.example.com:80/music.ram
|
| Reference |
"Ram Files and Ramgen" |
| Authenticated Ram File |
| Mount points |
Ram files are delivered by Web servers, and thus cannot be authenticated by RealServer. The files referenced by the Ram file, however, can be authenticated. |
| Link in Web page |
| Example |
SMIL Files
|
|
| Mount points |
none, for most links |
| Link in Web page |
http://address:HTTPPort/ramgen/path/file.smi
|
| Example |
http://realserver.example.com:8080/ramgen/music.smi
|
| Reference |
"SMIL Files" |
| Authenticated SMIL File |
| Mount points |
There are two methods of authenticating SMIL files or the files they reference. Refer to "Working with SMIL Files". |
| Link in Web page |
| Example |
Copyright © 2000
RealNetworks
For information on RealNetworks' technical support, click here.
Comments on this document? Click here.
This file last updated on 11/28/00 at 17:35:14.