Date: Fri, 2 Aug 2002 15:43:54 +0200 (CEST) From: Heiko Recktenwald <uzs106@ibm.rhrz.uni-bonn.de> To: Michael Nottebrock <michaelnottebrock@gmx.net> Cc: John Utz <john@utzweb.net>, multimedia@FreeBSD.ORG Subject: Re: href=rtsp Message-ID: <Pine.BSF.4.21.0208021538460.1169-100000@moritz.alleswirdgruener> In-Reply-To: <3D4A6075.6070704@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Nottebrock: > rtsp is a _protocol_, which could, in theory, carryall sorts of > content. It depends on the browser, it might allow plugins to make > themselves the default handler for a whole protocol. This is it. Like it is done with telnet urls. Without any mime. > Or it might > recognize the mime-type from the file extension, be it from a build-in This could be done too. > list or from a user-definition, but not the protocol, and as a > consequence feed the whole URL to the helper-application configured for > that mime-type. The behaviour of Netscape 4, should it be the way you > describe it and unchangably so would be quite braindead, but then - it's > Netscape 4. So, if we all had modern browsers, the use of mpeg video playlists would be limited to its use as a list. Clip, clip, clip, in a predefined order. Sotosay ascii movies. Ok for me ;-) Thanks, H. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0208021538460.1169-100000>