RE: [Uri-review] Request for review

On 7/7/2006, Martin Duerst <duerst@it.aoyama.ac.jp> wrote:

>At 07:04 06/07/06, Andrey Shur wrote:

>>Mark,
>>
>>If for the case the Uri like
>>http://www.example.org/foo/packages/my.package/my.part
>>would be published to the world, how then the information on the >my.package
>>actual location (residing in the database at
>>http://www.example.org/foo/packages.asp?name=my.package)
>>is obtained by a client?
>>
>>In other words how the published Uri is different from the Uri indicating
>>/my.part part in the package located at regular HTTP address:
>>http://www.example.org/foo/packages/my.package ?

>It's a very basic principle that URIs look like they refer
>to directory names and file names, but they don't have to.
>A server can do anything it wants behind the scenes.

>A typical example is to use a CGI script, but that CGI
>script wouldn't be
>http://www.example.org/foo/packages/my.package/my.part,
>but for example
>http://www.example.org/foo/packages.
>With the CGI interface, the rest of the path gets put
>into the ENV variable PATH_INFO, so the script then
>can make sure it serves the right part from the right
>package.

>There are numerous other techniques that produce similar
>results.

>Regards,   Martin.

Martin,
I thought previously we agreed that not touching server code and relying solely on the client code is a reasonable goal?

Regards
- Andrey

#-#-#  Martin J. Du"rst, Assoc. Professor, Aoyama Gakuin University
#-#-#  http://www.sw.it.aoyama.ac.jp       mailto:duerst@it.aoyama.ac.jp

_______________________________________________
Uri-review mailing list
Uri-review@ietf.org
https://www1.ietf.org/mailman/listinfo/uri-review