On Wed, 7 Jan 2004, Tim Showalter wrote:
> Actually, "a.b" "c.d" => "a.bc.d". I think this is a bug and it should
> be a.b.c.d. As the instigator of this change, I'm sure I didn't intend
> a.bc.d, but I was not particularly clever about the implementation here.
I don't agree, RFC3501 states:
If a server implementation has no concept of break out
characters, the canonical form is normally the reference
name appended with the mailbox name. Note that if the
server implements the namespace convention (section
5.1.2), "#" is a break out character and must be treated
as such.
So, while somewhat bizarre if you are viewing the reference argument as a
"current working directory", the specification certainly allows this
behavior.
And the specification specificaly addresses this case as well:
For example, a reference of "foo/bar" and
mailbox name of "rag/baz" could be interpreted as
"foo/bar/rag/baz", "foo/barrag/baz", or "foo/rag/baz".
Of course, the specification also says:
Note: The interpretation of the reference argument is
implementation-defined.
Which makes any client relying on a particular interpretation of the
reference argument without the user doing something somewhat questionable.
-Rob
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski | Andrew Systems Group * Research Systems Programmer
PGP:0x5CE32FCC | Cyert Hall 207 * [EMAIL PROTECTED] * 412.268.7456
-----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS/IT/CM/PA d- s+: a-- C++++$ ULS++++$ P+++$ L+++ E W+ N(-) o? K- w-- O-
M-- V-- PS+ PE+ Y+ PGP+ t+@ 5+++ X- R@ tv-- b+ DI+++ D++ G e++ h+ r- y?
------END GEEK CODE BLOCK-----
