No, but one could certainly treat lists referenced in this way as a part of
the data needed to run the script, and fetch them up front, before the
script begins executing. Of course, that presumes that one can "fetch" the
list. The problem becomes much worse when the list is a query-only
service, because then you're going to need to talk to the service while
running the script, and _that_ could fail.
For us at least, unfetchable lists are looking to be the rule, not the
exception.
I can't get into specifics, but we have one customer who is building an
application on top of the external lists mechanism and who has decided to use a
list of hashes rather than the original data in order to save space. Why?
Because they have calculated that if they store the original data they're going
to need 17 Gb more real memory in each of their database servers.
Ned
_______________________________________________
sieve mailing list
sieve(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/sieve