till schrieb:
On Tue, Jul 14, 2009 at 1:36 PM, emiemidaruma@gmail.com 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).
+1
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
hopefully you will agree ;-)
I think this would be the best solution. Starting with a simple filtering and leave it extensible. So now that turns me on but actually I don't know yet if I have the time to start writing a plugin for that - especially because I have to learn the plugin structure before (but it seems to be very clear).
Filtering was the first thing I missed in roundcube. I'll keep you informed ...
Cheers
Andy _______________________________________________ List info: http://lists.roundcube.net/dev/