Return-Path: 
 <dev-return-6677-apmail-apr-dev-archive=apr.apache.org@apr.apache.org>
Delivered-To: apmail-apr-dev-archive@apr.apache.org
Received: (qmail 15014 invoked by uid 500); 3 Jun 2002 15:39:25 -0000
Mailing-List: contact dev-help@apr.apache.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:dev@apr.apache.org>
List-Help: <mailto:dev-help@apr.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@apr.apache.org>
List-Subscribe: <mailto:dev-subscribe@apr.apache.org>
Delivered-To: mailing list dev@apr.apache.org
Received: (qmail 15003 invoked from network); 3 Jun 2002 15:39:25 -0000
Errors-To: <wrowe@rowe-clan.net>
Message-Id: <5.1.0.14.2.20020603102554.01edd080@pop3.rowe-clan.net>
X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Mon, 03 Jun 2002 10:33:28 -0500
To: Paul Marculescu <paul@p16.pub.ro>;, dev@apr.apache.org
From: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Subject: Re: [PATCH] apr_uri
In-Reply-To: <3CFB2017.68C9A5EB@p16.pub.ro>
References: 
 <Pine.LNX.4.44.0206022213110.117-100000@deepthought.cs.virginia.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

At 02:51 AM 6/3/2002, Paul replied:

>Cliff Woolley wrote:
> >
> > On Mon, 3 Jun 2002, Paul Marculescu wrote:
> >
> > > I made a little patch for apr-util's apr_uri.c to handle win32 absolute
> > > paths under file:// schema.
> >
> > I'll admit it strikes me as a bit odd to be supporting platform-specific
> > forms of _uniform_ resource identifiers.  :-)  Is this a
> > standards-recognized form or is it just one that Microsoft made up?  If
> > it's valid under the standard, then I suppose it makes sense to support
> > it.
>
>:)
>I think you are right, but suppose you're on a Win32 platform and you
>want to specify
>this path: D:/test in a file url. According to the standards, it will be
>file:///D:/test
>Right?
>
>The apr_uri_parse() function generates the path /D:/test from this URI.
>This is where I got a little confused, since rfc's said:
>
>  A file URL takes the form:
>   file://<host>/<path>
>  where <host> is the fully qualified domain name of the system on
>  which the <path> is accessible, and <path> is a hierarchical
>  directory path of the form <directory>/<directory>/.../<name>.
>
>so why is the '/' after the host included in the path?

It is... ever used Netscape?  They choose to follow the rfc (while encoding
the d: as d|... e.g. file:///d|/foo ... and unless that second colon is 
ambigious,
I'd suggest we support either : or | for consistency [the "|" is entirely 
invalid in
win32 paths, as are ">" and "<"].