[pLog-svn] r6088 - plog/branches/lifetype-1.2/class/security
markplace at gmail.com
Thu Nov 29 21:58:34 EST 2007
Here is a potential proposal that would solve this problem, and not
> require the filters to be run twice
> 1) Make it possible to have a plugin return the fact that some state has
> been persisted.
> 2) Set this as a property of the comment.
> 3) If one of the following plugins wants to delete the comment, it will
> call the Delete() method.
> 4) In this method it checks to see if the "something has been persisted"
> bit and doesn't actually delete the comment, but just hides it.
An alternative to this is to have the comment keep a reference to the
> filters that have persisted something. In the delete method, before the
> comment is deleted, all of the filters are given a chance to clean up their
Why can't we just put the bayesian filter in last order? it seems solve this
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pLog-svn