On Wed, Aug 19, 2009 at 11:00 PM, Steve Brewin<[email protected]> wrote: > Robert Burrell Donkin [mailto:[email protected]] wrote on: 19 > August 2009 11:31 > >> the sieve WG is thinking about standardising a 'list' test extension >> which allows a header value to be tested against an external list >> (perhaps JSON or FOAF loaded over HTTP, or a blacklist hosted in >> LDAP). i'd find this very useful so i plan to add an implementation to >> jsieve. >> >> sieve tests are very like matchers. so, i was wondering: >> >> 1. whether it might worthwhile doing a matcher at the same time >> 2. if so then - even though the matcher would be general purpose - if >> it'd be ok in be in sieve >> >> (this is a more general issue since mailets or matchers could be >> easily created from many of the sieve extensions) >> >> opinions? >> >> - robert > > Way back when I had time to genuinely contribute, my idea was to componetise > the logic of matchers, mailets and Sieve extensions, and use adapters to > make available the logic to each. This would maximise reuse and deliver a > common set of behaviours. > > Maybe we need a commons project for the logic with the adapters living in > their respective projects?
yes - this sounds like the right approach - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
