I was hoping that wget supported RTSP. When I looked I found the following:
I don`t think rtsp is appropriate to wget. Other sources may reference
rtsp:// URL`s, but once you`ve got it I think you can really only talk to
the stream(s) offered by that URL. (Until somebody develops an
audio/video transport that has embedded URL`s that need to be
extracted :-) ).
Maybe I don't get what this says, but wget doesn't understand ("get" har)
HTML or .jpg or .iso either, but it is eliminately useful for snagging
such files.
I think that the same is true for .rpm, .mpg, etc. sitting on the other
side of an RSTP connection.
To get to the point, I am on the wrong end of a 56k connection, and would
like to be able to view high-quality Real Media and MPEG movies that are
only available via RTSP, and all RTSP clients (players) that I am aware of
just choke . . . they won't save the file to disk or buffer the entire
file (six of one, half a dozen of the other) before playing.
Arguments for:
- TODO says "* Add more protocols (e.g. gopher and news), implementing
them in a modular fashion." Adding RTSP seems to fit the project
philosophy.
- RTSP is quite HTTP like, so it sort of fits within the scope of the
project. (Unlike adding something like IMAP support :-P )
- It would be super useful, and wget is all about being useful IMO.
Arguments against (with rebuttals):
- RTSP is a proprietary protocol. (Nope, it is covered by RFC 2326)
- RTSP is only used by Real, and they suck because they give away a free
player that isn't Free Software. (Nope, anybody can use it. Maybe they
do suck, but it is irrelevant.)
I'm the worst programmer in the world, and I don't have much time on my
hands, but I will see what I can do in terms of a patch.
I'm looking forward to feedback.
-Peter
--
Get my PGP key at
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x76CA8A59 Fingerprint:
6128 5651 6F23 EC17 6EBD 737D 960A 20E6 76CA 8A59
