On Tue, 16 Sep 2003, Pete Maclean wrote: > Consider a store that can contain email messages, appointments, addresses, > notes, etcetera, with items of each class restricted to separate containers > but with all such containers in a common hierarchy. Am I correct in > thinking that this would be an example of a situation where the foo/ issue > arises? If so, then I well appreciate the desirability of a client's being > able to determine that it is unable to create a mailbox called, say, > Reminders because there happens to already be a notes-container with that > same name. I am not sure that I like the solution though.
Yes, that's one scenario. I outlined another scenario in the message. > But there is still something I seem to be missing. Is the idea that a > server should list such non-mail containers in, say, a LIST "" * or only in > a specific case such as LIST "" Reminders/%? I would think that "*" should always show all names. But the issue isn't that; it's the specific case of name/% or name/* where "name" exists as a non-terminal level of hierarchy but has no children. My argument basically says that if name exists, then name/% or name/% should always result in non-empty LIST output. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
