On Tue, Jul 14, 2009 at 1:36 PM, emi<[email protected]> wrote: > Hi, > If you're going to do a filter plugin, I see three ways to do so: > * Implement a unique plugin that will be able to handle multiple filtering > systems (client-side, sieve, exim, etc) > * Implement multiple plugins, one for each filtering system > * Implement one general plugin with some hooks (Filter API) where each > particular plugin (client-side, sieve, etc) would use them > > Just as a suggestion, I recommend to implement the simpler one (just > client-side filtering plugin, as you say) and then see wich of these options > is better/easier to implement and to manage. Personally, I'd prefer the > thirst solution, which is extensible, clearer and faster (I suppose).
I'm inclined to agree. :-) I wanted to write a plugin for dspam as well. I think providing an "internal" filter API and offering drivers would be the best solution, but that's just my personal opinion. Till _______________________________________________ List info: http://lists.roundcube.net/dev/
