Hi Barry,
That makes sense. Please consider my concern resolved.
Thanks
Suresh
On 11-06-07 06:36 PM, Barry Leiba wrote:
Thanks, Suresh, for the review.
This following text is a bit handwavy. Is this by design? How can the sieve
implementation identify the list as one that has an open subscriber list. Is
the sieve engine expected to try one of these methods first and failover
into another. Is there an expectation that all sieve implementations will
actually be capable of invoking both these mechanisms?
"For some lists, the Sieve engine might directly retrieve the list and
make its own comparison. Other lists might not work that way -- they
might provide a way to ask if a value is in the list, but not permit
retrieval of the list itself."
Yes, it's vague by design. The Sieve engine needs to be integrated
with the list handling -- this is saying that for some that's done
simply by having the Sieve engine retrieve the list and search it, but
for other lists it's done through some sort of API by which it
searches the list. In any case, the Sieve engine needs to know how to
access each list that it supports... and that access is out of scope
here.
Barry
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
