Not that this whole issue is relevant, but I need to know the
answers anyway --
What's the exact difference between src and qtsrc? I was fiddling
around with qtsrc to keep WMP in IE from grabbing EMBEDs that
absolutely have to go to Quicktime, even if WMP has a handler for the
content type.
From <http://developer.apple.com/documentation/QuickTime/
Conceptual/QTScripting_HTML/index.html?http://developer.apple.com/
documentation/QuickTime/Conceptual/QTScripting_HTML/
QTScripting_HTML_Document/chapter_1000_section_3.html> :
Causes the plug-in to ignore the movie specified in the SRC
parameter; instead QuickTime plays the file specified in QTSRC. This
allows you to specify one file to cause the browser to load
QuickTime, then tell QuickTime to play another file, even if the
browser would not normally choose QuickTime for the file you want to
play.
This is useful for playing media other than QuickTime movies, such as
MP3 audio, MPEG-4 video, and SMIL files.
QTSRC is also useful for specifying rtsp:// streams. Browsers
typically choose a single application to handle all rtsp:// URLs,
regardless of the file type or MIME type. Setting the SRC parameter
to the http:// URL of a QuickTime movie, and setting QTSRC to the
rtsp:// URL, causes the browser to load QuickTime, then causes
QuickTime to load the rtsp:// URL.
Note that the browser may download the file specified in the SRC
parameter, even though the plug-in ignores it. For this reason, you
should always specify a small file in the SRC parameter when using
QTSRC.
WARNING: Many browsers simply pass the contents of the SRC parameter
to the plug-in, but other browsers either verify that the SRC URL is
valid or actually download the specified SRC URL. If you specify a
“dummy” URL in the SRC parameter, many browsers will successfully
load QuickTime and display the movie specified in QTSRC, but other
browsers will not. Be sure to pass the URL of an actual file in the
SRC parameter; a small file is best, in case the browser downloads it.
