OK, this one has me stumped.
Imagine that as a client you get this as part of a response to a LIST
command:
-------------------------- Cut here ----------------------------
* LIST () "/" "Public Folders/Busi 3923C2/Carisa Lloyd"
-------------------------- Cut here ----------------------------
Is it legal to receive this response without also at some point receiving
this as well?
-------------------------- Cut here ----------------------------
* LIST () "/" "Public Folders/Busi 3923C2"
-------------------------- Cut here ----------------------------
In other words, can a LIST response implicitly create a level of
hierarchy? If so, how can you know what attributes the implicit hierarchy
element has without specifically re-querying for it?
I'm currently seeing this behaviour from Exchange Server 2003, and it's
throwing out my code quite severely. Before I add a lot of code to
handle this, I want to be sure that it's legal and that I'm not just creating
a rod for my back at some later stage.
If this *is* legal, I really think the RFC needs to be updated to reflect it,
because I hardly think it can be considered "intuitive".
Cheers!
-- David --
------------------ David Harris -+- Pegasus Mail ----------------------
Box 5451, Dunedin, New Zealand | e-mail: [EMAIL PROTECTED]
Phone: +64 3 453-6880 | Fax: +64 3 453-6612
Sign seen at a tailor's in Rhodes:
"Order your summers suit. Because is big rush, we will
execute customers in strict rotation."
--
-----------------------------------------------------------------
For information about this mailing list, and its archives, see:
http://www.washington.edu/imap/imap-list.html
-----------------------------------------------------------------
