Re: IMAP URLs

Martin J Duerst <mduerst@ifi.unizh.ch> Mon, 18 November 1996 09:36 UTC

Received: from cnri by ietf.org id aa01871; 18 Nov 96 4:36 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa05425; 18 Nov 96 4:36 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id EAA24464 for uri-out; Mon, 18 Nov 1996 04:24:16 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id EAA24459 for <uri@services.bunyip.com>; Mon, 18 Nov 1996 04:24:11 -0500
Received: from josef.ifi.unizh.ch by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA11607 (mail destined for uri@services.bunyip.com); Mon, 18 Nov 96 04:23:56 -0500
Received: from ifi.unizh.ch by josef.ifi.unizh.ch id <00380-0@josef.ifi.unizh.ch>; Mon, 18 Nov 1996 10:23:47 +0100
Subject: Re: IMAP URLs
To: Chris Newman <Chris.Newman@innosoft.com>
Date: Mon, 18 Nov 1996 10:23:45 +0100 (MET)
Cc: uri@bunyip.com
In-Reply-To: <Pine.SOL.3.95.961117151842.29171E-100000@eleanor.innosoft.com> from "Chris Newman" at Nov 17, 96 03:33:03 pm
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1344
From: Martin J Duerst <mduerst@ifi.unizh.ch>
Message-Id: <"josef.ifi..985:18.10.96.09.23.48"@ifi.unizh.ch>
Sender: owner-uri@bunyip.com
Precedence: bulk

Chris Newman wrote:

>I also believe there is a bug in RFC 1808 with respect to multiple
>parameters.  I think the relative URL should inherit all parameters form
>the base URL, except those that are specified in the relative URL.  The
>current spec indicates that if *any* parameter is present in the relative
>URL, it overrides all parameters in the base URL.  Comments?

For some cases, it looks simpler if parameter values are inherited
individually. But there are two problems.

The first problem is one of convenience: In some cases, parameters
stay almost the same, and only a value or two changes. In other
cases, the names of parameters can change widely even if the
rest of the URL stays the same. For these cases, the spec according
to RFC 1808 is definitely more convenient.

The second problem is somewhat more basic: If you want to change
a list of parameters, how do you indicate the absence of a parameter?
One possibility would be to indicate the parameter again, with an
empty value, but in some cases, an empty parameter value and the
complete absence of the parameter will not mean the same.

Therefore, it looks very much like the specification for not
partially inheriting parameters as in RFC 1808 makes a lot of
sence, and is definitely not a bug, even if in some cases,
it may not exactly be optimal.

Regards, Martin.