At 4:53 PM -0500 3/28/97, Tim Showalter wrote:
I'd like to allow nested conditionals -- this makes things a little bit more
complicated. Also, guaranteeing the order of evaluation might be useful,
but might be difficult to work out with ACAP.
I think we really need to focus on keeping the base spec simple, and
compatible with IMAP and ACAP. The simplest way to store the filters in
ACAP would be as one attribute, in the user's options dataset. That would
give you the explicit ordering you want, but would make it a bit difficult
for some clients to deal with very long sets of filters. The other
approach I see is to store each filter rule in its own attribute. Ordering
could be enforced by an extra attribute (execute-order) which would contain
a number.