Re: Format of RTSP URLs
"Roy T. Fielding" <fielding@kiwi.ics.uci.edu> Tue, 15 July 1997 18:38 UTC
Received: from cnri by ietf.org id aa15513; 15 Jul 97 14:38 EDT
Received: from services.bunyip.com (services.Bunyip.Com [192.77.55.2]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid OAA05255; Tue, 15 Jul 1997 14:37:43 -0400 (EDT)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id OAA08395 for uri-out; Tue, 15 Jul 1997 14:21:05 -0400 (EDT)
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.8.5/8.8.5) with ESMTP id OAA08388 for <uri@services.bunyip.com>; Tue, 15 Jul 1997 14:21:02 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id OAA25332 for uri@services; Tue, 15 Jul 1997 14:21:02 -0400 (EDT)
Received: from paris.ics.uci.edu (paris.ics.uci.edu [128.195.1.50]) by mocha.bunyip.com (8.8.5/8.8.5) with SMTP id OAA25329 for <uri@bunyip.com>; Tue, 15 Jul 1997 14:21:00 -0400 (EDT)
Received: from kiwi.ics.uci.edu by paris.ics.uci.edu id aa06322; 15 Jul 97 11:14 PDT
To: Rob Lanphier <robla@prognet.com>
cc: www-talk@w3.org, uri@bunyip.com, confctrl@isi.edu
Subject: Re: Format of RTSP URLs
In-reply-to: Your message of "Tue, 15 Jul 1997 09:50:28 PDT." <3.0.32.19970715095024.01322938@mail.prognet.com>
Date: Tue, 15 Jul 1997 11:03:09 -0700
From: "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>
Message-ID: <9707151114.aa06322@paris.ics.uci.edu>
Sender: owner-uri@bunyip.com
Precedence: bulk
>I think this may be acceptable, but there's one other possible requirement >I'd like to mention. It would be nice to have the ability to have relative >URLs, so that, for example, the following scenario can play out (using ":" >as a server side fragment identifier for the time being) > >C->S DESCRIBE rtsp://foo/db/moviebase?movie=twister RTSP/1.0 1 > >S->C RTSP/1.0 200 1 OK > Content-length: 178 > Content-type: application/sdp > > s= sample rtsp presentation > r = rtsp://foo/db/moviebase?movie=twister /* aggregate URL*/ > m= audio 0 RTP/AVP 0 > r = :track=audio1 /* URL to control audio*/ > m=video 0 RTP?AVP 26 > r = :track=video1 /* URL to control video*/ > >At this point, the client can easily discern that the audio track and the >video track are indeed merely fragments of the same object on the server, >and not separately controlled entities. I'm not sure how this would work >with ";" parameters, since the relative behavior defined in 1808 is >different than what I'd expect above (which is more akin to "#"). Those relative URLs would resolve to rtsp://foo/db/:track=audio1 rtsp://foo/db/:track=video1 which is obviously not what you would want. Query info and relative references do not mix in practice. In any case, using query info to select a resource, as opposed to redirecting to the real resource URL, is poor namespace management. ....Roy
- Format of RTSP URLs Rob Lanphier
- Re: Format of RTSP URLs Bill Simpson-Young
- Re: Format of RTSP URLs Rob Lanphier
- Re: Format of RTSP URLs Roy T. Fielding
- Re: Format of RTSP URLs Roy T. Fielding
- Re: Format of RTSP URLs Rob Lanphier
- Re: Format of RTSP URLs Roy T. Fielding
- Re: Format of RTSP URLs Bill Simpson-Young
- Re: Format of RTSP URLs Rob Lanphier
- RE: Format of RTSP URLs Brad Hefta-Gaub
- Re: Format of RTSP URLs Roy T. Fielding