Neystadt, John (John@comverse.com)
Thu, 13 Dec 2001 18:08:41 +0200
> >> This could be done by an IMAP extension for VPIM. Since
> >> Message-Context is
> >> not a MIME base header it probably does not belong in the
> >> SORT base document.
> >
> > Marc, the SORT itself is a draft. Why do a separate effort
> and not include
> > it straight in SORT? BTW: I've tried to look in archives and did not
> > found a discussion of including a generic HEADER keyword
> discussion for
> > SORT. Why not allow sorting by ANY header?
I would suggest that sorting by header value has the following semantics:
1. Take plain header value without parameters and comments (i.e. strip off
all '; xxx=yyy')
2. Determine charset from header itself (according to 2047) or us-ascii by
default.
3. Use same collation mechanism as for other comparators.
> That would be reasonable but how do you do the sort comparison? Some
> headers, e.g. Priority, have a particular set of values with a clear
> ordering that is not a simple ascii sort which is all the
> current SORT can
> do. I suspect we will have to add comparators to SORT to satisfy i18n
> issues.
I think this is simplere and better than not to support anything. In my
opinion either this or a specific comparator for Message-Context is
required.
> >> > 2. IMAP: Add support for UIDs in unsolicited events
> >>
> >> This can't be done without breaking IMAP2 compatibility.
> >> IMAP2 clients are
> >> not extinct yet. We've learned that the hard way.
> >
> > Why? If we introduce a new UIDIDLE capability and syntax of
> >
> > tag UID IDLE
> >
> > with new untagged responses, like:
> >
> > S: * 44 UID EXPUNGE
> > S: * 108 UID FETCH (FLAGS (\Seen))
> >
> > This will not affect existing clients.
>
> But it doesn't completely solve the problem because untagged
> responses can
> come back outside of IDLE and those will still only have
> sequence number.
> The only way to do this properly is to have a switch on the
> SELECT command
> to turn on this behaviour.
I think this is a good idea, and trying to take it further, we can add an
option to SELECT to block unsolicited events completely and allow them only
in IDLE (or UID IDLE) mode. Once most servers implement this a big burden
will be shifted from clients' developers.
John Neystadt
john@neystadt.org
http://www.neystadt.org/john/
This archive was generated by hypermail 2.0b3 on Thu Dec 13 2001 - 18:22:25 IST