Re: Format of RTSP URLs
"Roy T. Fielding" <fielding@kiwi.ics.uci.edu> Tue, 15 July 1997 20:06 UTC
Received: from cnri by ietf.org id aa17354; 15 Jul 97 16:06 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 QAA05663; Tue, 15 Jul 1997 16:04:47 -0400 (EDT)
Received: (from daemon@localhost) by services.bunyip.com (8.8.5/8.8.5) id PAA09666 for uri-out; Tue, 15 Jul 1997 15:40:14 -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 PAA09661 for <uri@services.bunyip.com>; Tue, 15 Jul 1997 15:40:11 -0400 (EDT)
Received: (from daemon@localhost) by mocha.bunyip.com (8.8.5/8.8.5) id PAA26105 for uri@services; Tue, 15 Jul 1997 15:40:11 -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 PAA26096 for <uri@bunyip.com>; Tue, 15 Jul 1997 15:40:05 -0400 (EDT)
Received: from kiwi.ics.uci.edu by paris.ics.uci.edu id aa13146; 15 Jul 97 12:29 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 11:52:44 PDT." <3.0.32.19970715115243.013248c8@mail.prognet.com>
Date: Tue, 15 Jul 1997 12:18:41 -0700
From: "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>
Message-ID: <9707151229.aa13146@paris.ics.uci.edu>
Sender: owner-uri@bunyip.com
Precedence: bulk
>I'm not aware that there is currently a spec for server-side fragments (and >colons beyond the port position of an URL), which is what I'm suggesting is >a necessary feature for relative URLs to work. I would expect that the >rules that apply to client-side fragments ("#whatever") would also apply to >server-side fragments. Except that they don't. You can't just invent a new syntax because it is convenient to do so -- existing implementations must be taken into account, and for all existing implementations > rtsp://foo/db/moviebase?movie=twister:track=audio1 has a query part of "movie=twister:track=audio1" because ":" is not a reserved character within the query portion of a URL. Furthermore, the scheme-independent relative URL resolution algorithm calls for the query component of the base URL to be stripped off BEFORE it is used for relative resolution, since that is what current practice does. It is therefore impossible for us to introduce such a component to the URL syntax. >> In any case, using query info to >>select a resource, as opposed to redirecting to the real resource URL, >>is poor namespace management. > >It may be the case that the real resource is stored in a database that must >be accessed via query. Then the query should return a redirect to a new URL, or the namespace should be structured such that it maps into a database query. There is no significant difference between the server-side implementations of rtsp://foo/db/moviebase?movie=twister:track=audio1 and rtsp://foo/db/moviebase/twister/track=audio1 It is merely an issue of how the server manages its namespace. If you want to use relative forms, you must use the latter syntax. ....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