On Tue, 2004-05-04 at 22:11, Mike Wener wrote: > > Whether that means anything today is open to debate; but it may mean > > something tommorrow, and at the very least your client has to handle > > it well enough to ignore it. > > How would this become clearly defined? Is it a matter of convention or > specification? For example, I could envision a server issuing a LIST > Response in response to a CREATE. A client could then use this while > tracking unsolicited respones.
I think clients should already try to implement them meaningfully. So that it updates it's internal cache and if the information is already visible to user in some way, it would also be updated. So if server wants to, it could then automatically send some notifications: - STATUS whenever mailbox changes - LIST whenever new mailboxes appear or existing ones change (eg. \NoSelect flag gets dropped) - LSUB whenever another session has subscribed to a mailbox Too bad LIST/LSUB can't tell that mailbox was deleted/unsubscribed.
signature.asc
Description: This is a digitally signed message part
